Sign git tags &amp; commits #226

@rugk commented on GitHub (Jan 13, 2017):

When tags are manually done you can easily sign them. That's all I request.
Of course signing the binary files would also be nice, but that's another thing.

@rugk commented on GitHub (Jan 13, 2017): When tags are manually done you can easily sign them. That's all I request. Of course signing the binary files would also be nice, but that's another thing.

GiteaMirror commented

@tboerger commented on GitHub (Jan 13, 2017):

So everybody should integrate his GPG key into git and sign the commits. I have added this snippet to my .gitconfig now, so from now on every tag I publish will be signed by me:

[alias]
  tag = tag -s

For everybody who is interested, I'm using https://github.com/tboerger/homeshick-base/blob/master/home/.gitconfig as my ~/.gitconfig and additionally to that I put this into ~/.gitconfig.local

[commit]
  gpgSign = true

@tboerger commented on GitHub (Jan 13, 2017): So everybody should integrate his GPG key into git and sign the commits. I have added this snippet to my `.gitconfig` now, so from now on every tag I publish will be signed by me: ``` [alias] tag = tag -s ``` For everybody who is interested, I'm using https://github.com/tboerger/homeshick-base/blob/master/home/.gitconfig as my `~/.gitconfig` and additionally to that I put this into `~/.gitconfig.local` ``` [commit] gpgSign = true ```

GiteaMirror commented

@lunny commented on GitHub (May 4, 2017):

since https://github.com/go-gitea/gitea/issues/425 has been resolved. This issue should be resolved also or it's easy to fix now?

@lunny commented on GitHub (May 4, 2017): since https://github.com/go-gitea/gitea/issues/425 has been resolved. This issue should be resolved also or it's easy to fix now?

GiteaMirror commented

@tboerger commented on GitHub (May 4, 2017):

The releases done by me are based on signed tags already.

@tboerger commented on GitHub (May 4, 2017): The releases done by me are based on signed tags already.

GiteaMirror commented

@tboerger commented on GitHub (May 4, 2017):

since #425 has been resolved. This issue should be resolved also or it's easy to fix now?

That's a totally different story. He just requested to sign our Gitea tags and binaries.

@tboerger commented on GitHub (May 4, 2017): > since #425 has been resolved. This issue should be resolved also or it's easy to fix now? That's a totally different story. He just requested to sign our Gitea tags and binaries.

GiteaMirror commented

@lunny commented on GitHub (May 4, 2017):

Ohoh, So this is a build thing not a feature?

@lunny commented on GitHub (May 4, 2017): Ohoh, So this is a build thing not a feature?

GiteaMirror commented

@bkcsoft commented on GitHub (May 4, 2017):

Yeah, and I'm signing my tags. Maybe close when we have a HOWTO_RELEASE.md ? 😄

@bkcsoft commented on GitHub (May 4, 2017): Yeah, and I'm signing my tags. Maybe close when we have a `HOWTO_RELEASE.md` ? 😄

GiteaMirror commented

@agaida commented on GitHub (Nov 29, 2017):

an annotated or signed tag would be helpful for the upcoming release - git describe start to look a little bit strange as the latest annotated or signed tag was v1.1.0 - v1.1.0-783-g183da4c2

@agaida commented on GitHub (Nov 29, 2017): an annotated or signed tag would be helpful for the upcoming release - git describe start to look a little bit strange as the latest annotated or signed tag was v1.1.0 - v1.1.0-783-g183da4c2

GiteaMirror commented

@tboerger commented on GitHub (Nov 29, 2017):

All tags should be signed and annotated since 1.1.3, otherwise somebody made a mistake :)

@tboerger commented on GitHub (Nov 29, 2017): All tags should be signed and annotated since 1.1.3, otherwise somebody made a mistake :)

GiteaMirror commented

@tboerger commented on GitHub (Nov 29, 2017):

@tboerger commented on GitHub (Nov 29, 2017): <img width="982" alt="bildschirmfoto 2017-11-29 um 16 28 04" src="https://user-images.githubusercontent.com/156964/33382931-5211a7fa-d522-11e7-99fa-2e662a9c7167.png">

GiteaMirror commented

@lafriks commented on GitHub (Nov 29, 2017):

I think we can close the issue as we are already doing it

@lafriks commented on GitHub (Nov 29, 2017): I think we can close the issue as we are already doing it

GiteaMirror commented

@agaida commented on GitHub (Nov 29, 2017):

thats fine - but the last tag related to master was v1.1.0 by some webhippie - and if one follow the current development it looks like that:

% git describe
v1.1.0-815-g033ad9a7

maybe this could be changed, 1.1.0 + 815 commits is nice and precise - ok, speed in Ansgström/Week is also precise.

@agaida commented on GitHub (Nov 29, 2017): thats fine - but the last tag related to master was v1.1.0 by some webhippie - and if one follow the current development it looks like that: > % git describe > v1.1.0-815-g033ad9a7 maybe this could be changed, 1.1.0 + 815 commits is nice and precise - ok, speed in Ansgström/Week is also precise.

GiteaMirror commented

@lafriks commented on GitHub (Nov 29, 2017):

We do not tag on master branch but on release/* branches

@lafriks commented on GitHub (Nov 29, 2017): We do not tag on master branch but on release/* branches

GiteaMirror commented

@agaida commented on GitHub (Nov 29, 2017):

you have - the last tag on master is v1.1.0 - but anyways ...

@agaida commented on GitHub (Nov 29, 2017): you have - the last tag on master is v1.1.0 - but anyways ...

GiteaMirror commented