[ANN] git-phoenix - repository recovery tool

[ANN] git-phoenix - repository recovery tool

[Daniil Iaitskov]

Hi Git List,

I would like to share a tool for recovery an unpublished Git repository 
after accidental removal or file system failure. VCS usually implies 
backup feature auto of the box, but due to Git decentralized nature and 
developer's laziness source code sometimes can be lost. Recently I 
accidentally deleted all projects, including a few unpulished POCs, 
after infamous rm -rf * typo. Work on them has been interrupted for 
quite awhile and rewriting them from scratch recalling all the hack 
intricacies would be terribly boring. So I decided to invest my dev time 
in a more creative way.

https://github.com/yaitskov/git-phoenix/


Best regards,

Daniil Iaitskov

Re: [ANN] git-phoenix - repository recovery tool

[Christian Couder]

Hi Daniil,

On Thu, Jul 24, 2025 at 8:49 PM Daniil Iaitskov <dyaitskov@gmail.com> wrote:
>
> Hi Git List,
>
> I would like to share a tool for recovery an unpublished Git repository
> after accidental removal or file system failure. VCS usually implies
> backup feature auto of the box, but due to Git decentralized nature and
> developer's laziness source code sometimes can be lost. Recently I
> accidentally deleted all projects, including a few unpulished POCs,
> after infamous rm -rf * typo. Work on them has been interrupted for
> quite awhile and rewriting them from scratch recalling all the hack
> intricacies would be terribly boring. So I decided to invest my dev time
> in a more creative way.
>
> https://github.com/yaitskov/git-phoenix/

Thanks for creating it. It doesn't seem to have a license, which might
prevent some of us from using it, though.

Anyway for now there is the following pull request to talk about it in
the next Git Rev News edition:

https://github.com/git/git.github.io/pull/790

Best,
Christian.

Re: [ANN] git-phoenix - repository recovery tool

[Daniil Iaitskov]

On 7/25/25 10:12, Christian Couder wrote:
> Hi Daniil,
> 
> On Thu, Jul 24, 2025 at 8:49 PM Daniil Iaitskov <dyaitskov@gmail.com> wrote:
>>
>> Hi Git List,
>>
>> I would like to share a tool for recovery an unpublished Git repository
>> after accidental removal or file system failure. VCS usually implies
>> backup feature auto of the box, but due to Git decentralized nature and
>> developer's laziness source code sometimes can be lost. Recently I
>> accidentally deleted all projects, including a few unpulished POCs,
>> after infamous rm -rf * typo. Work on them has been interrupted for
>> quite awhile and rewriting them from scratch recalling all the hack
>> intricacies would be terribly boring. So I decided to invest my dev time
>> in a more creative way.
>>
>> https://github.com/yaitskov/git-phoenix/
> 
> Thanks for creating it. It doesn't seem to have a license, which might
> prevent some of us from using it, though.

License is specified in project file (BSD3):
https://github.com/yaitskov/git-phoenix/blob/9a88c55fd45f28d4e1865df3ac746b409474eaf7/git-phoenix.cabal#L135

The tool is also published on hackage under BSD3:
https://hackage.haskell.org/package/git-phoenix-0.0.2

I don't see much difference between open source licenses and picked BSD3 
just because it is popular here.

What license would like to see?

> 
> Anyway for now there is the following pull request to talk about it in
> the next Git Rev News edition:
> 
> https://github.com/git/git.github.io/pull/790
> 
> Best,
> Christian.

Best regards,
Daniil Iaitskov

Re: [ANN] git-phoenix - repository recovery tool

[Christian Couder]

On Fri, Jul 25, 2025 at 8:40 PM Daniil Iaitskov <dyaitskov@gmail.com> wrote:
>
> On 7/25/25 10:12, Christian Couder wrote:

> > Thanks for creating it. It doesn't seem to have a license, which might
> > prevent some of us from using it, though.
>
> License is specified in project file (BSD3):
> https://github.com/yaitskov/git-phoenix/blob/9a88c55fd45f28d4e1865df3ac746b409474eaf7/git-phoenix.cabal#L135

Ok, I just saw that GitHub didn't display the license information at
the top of your repository page, and then only took a look at the
README where I couldn't find any license information.

It seems that you need to add a file named LICENSE (or LICENSE.txt,
LICENSE.md) with the full text of your chosen license in the root
directory of your repository for GitHub to automatically detect and
display it. I could help people find that information and be more
confident that they can use it.

> The tool is also published on hackage under BSD3:
> https://hackage.haskell.org/package/git-phoenix-0.0.2
>
> I don't see much difference between open source licenses and picked BSD3
> just because it is popular here.
>
> What license would like to see?

It's your choice and I don't have any say in it, but I am happy that
it is open source :-)

Thanks.

Re: [ANN] git-phoenix - repository recovery tool

[Daniil Iaitskov]

On 7/25/25 11:01, Christian Couder wrote:
> On Fri, Jul 25, 2025 at 8:40 PM Daniil Iaitskov <dyaitskov@gmail.com> wrote:
>>
>> On 7/25/25 10:12, Christian Couder wrote:
> 
>>> Thanks for creating it. It doesn't seem to have a license, which might
>>> prevent some of us from using it, though.
>>
>> License is specified in project file (BSD3):
>> https://github.com/yaitskov/git-phoenix/blob/9a88c55fd45f28d4e1865df3ac746b409474eaf7/git-phoenix.cabal#L135
> 
> Ok, I just saw that GitHub didn't display the license information at
> the top of your repository page, and then only took a look at the
> README where I couldn't find any license information.
> 
> It seems that you need to add a file named LICENSE (or LICENSE.txt,
> LICENSE.md) with the full text of your chosen license in the root
> directory of your repository for GitHub to automatically detect and
> display it. I could help people find that information and be more
> confident that they can use it.

Thanks for feedback.
After getting familiar with content of a few BSD3 license files
I was able to commit mine.


> 
>> The tool is also published on hackage under BSD3:
>> https://hackage.haskell.org/package/git-phoenix-0.0.2
>>
>> I don't see much difference between open source licenses and picked BSD3
>> just because it is popular here.
>>
>> What license would like to see?
> 
> It's your choice and I don't have any say in it, but I am happy that
> it is open source :-)
> 
> Thanks.