Git files hidden in plain sight • Hacker News Board

Re: Git files hidden in plain sight

#41

Post by loeg » Tue, Aug 01, 2023, 4:55 PM UTC

remram wrote: post #37

loeg wrote: post #31

Earlier quoted context omitted.

Huh, is that true? If you push a new version of a tag, Github will ignore it? Or if you 'git fetch', git does not update tags? I would be pretty surprised at either of those.

It's the second one

I don't think so. In both cases, there was visible UI of either the new tag or that the tag was changed.

Github shows the updated tag.

git pull --tags shows:

  ! [rejected]           ->   (would clobber existing tag)

git pull --tags --force updates the tag.

Re: Git files hidden in plain sight

#42

Post by loeg » Tue, Aug 01, 2023, 4:57 PM UTC

WorldMaker wrote: post #36

loeg wrote: post #31

Earlier quoted context omitted.

Huh, is that true? If you push a new version of a tag, Github will ignore it? Or if you 'git fetch', git does not update tags? I would be pretty surprised at either of those.

All tag updates require a force push and any existing clones also need a force pull.

I agree. It is not the case that "most things ... won't check for updates to a tag," which is what GP claimed and I responded to. Most things do check for updates! Without checking, they could not warn you about / reject updates.

Re: Git files hidden in plain sight

#43

Post by remram » Tue, Aug 01, 2023, 5:13 PM UTC

loeg wrote: post #41

remram wrote: post #37

Earlier quoted context omitted.

It's the second one

I don't think so. In both cases, there was visible UI of either the new tag or that the tag was changed. Github shows the updated tag. git pull --tags shows: ! [rejected] -> (would clobber existing tag) git pull --tags --force updates the tag.

You asked about `git fetch`. If you change your question to `git pull --tags` then yes, the answer is different.

Re: Git files hidden in plain sight

#44

Post by loeg » Tue, Aug 01, 2023, 5:26 PM UTC

remram wrote: post #43

loeg wrote: post #41

Earlier quoted context omitted.

I don't think so. In both cases, there was visible UI of either the new tag or that the tag was changed. Github shows the updated tag. git pull --tags shows: ! [rejected] -> (would clobber existing tag) git pull --tags --force updates the tag.

You asked about `git fetch`. If you change your question to `git pull --tags` then yes, the answer is different.

git fetch --tags presents the exact same warning/error.

Re: Git files hidden in plain sight

#45

Post by WorldMaker » Tue, Aug 01, 2023, 5:27 PM UTC

loeg wrote: post #42

WorldMaker wrote: post #36

Earlier quoted context omitted.

All tag updates require a force push and any existing clones also need a force pull.

I agree. It is not the case that "most things ... won't check for updates to a tag," which is what GP claimed and I responded to. Most things do check for updates! Without checking, they could not warn you about / reject updates.

The trick to remember though is that new clones don't have any "update" check, they only see and fetch the latest value. There's no force push audit log for git refs in most git server software, there's just "local and remote refs disagree". That's not really an "update check" from the perspective of "having an update notification or update event".

Re: Git files hidden in plain sight

#46

Post by theamk » Tue, Aug 01, 2023, 5:38 PM UTC

talkingtab wrote: post #24

Is this a git issue or a github issue? I know git is being (mis)used, but the issues seem to be with github. Maybe a better title for those of us with no interest in github would be "Github hides git files in plain sight" ?

that functionality is pretty useful -- we use hidden refs (but more garden variety, pointing to commits) for all sorts of things, such as source revision for every CI run and past revisions of PRs.

Works really great -- the UI is not cluttered with thousands of rarely-used entries, but all the data is still backed up and usable witth git tools. Now if only github actions could support this...

Re: Git files hidden in plain sight

#47

Post by tambourine_man » Tue, Aug 01, 2023, 6:22 PM UTC

FrostKiwi wrote: post #20

tambourine_man wrote: post #19

But I want to know how they used figlet to generate ANSI colored image. Is that a custom font?

These are standard blocks available in any font. Just search for ANSI or ASCI art image converter and you will find many cli-tools and webapps allowing you to convert images to those ascii blocks.

I misread it, it’s just cating a text file. Thanks.

Re: Git files hidden in plain sight

#48

Post by remram » Tue, Aug 01, 2023, 8:03 PM UTC

loeg wrote: post #44

remram wrote: post #43

Earlier quoted context omitted.

You asked about `git fetch`. If you change your question to `git pull --tags` then yes, the answer is different.

git fetch --tags presents the exact same warning/error.

That's right.

> if you 'git fetch', git does not update tags? I would be pretty surprised

This is the comment you replied to:

> By default, most things assume that tags are immutable and won't check for updates to a tag.

You can use options to change from the default. I don't know what point you are now trying to make, but this conversation is getting very laborious.

Re: Git files hidden in plain sight

#49

Post by riformareov » Wed, Aug 02, 2023, 7:54 PM UTC

The concept of hidden files lurking within a repository, even after deletion, is both intriguing and concerning. The detailed walkthrough of how these hidden files can be discovered and the explanation of how they persist even after being removed from the working directory provide a clear understanding of the issue.