[pkg-go] You are not allowed to push code to this project

[Alexandre Viau]

On 2018-06-15 11:54 PM, Tong Sun wrote:
> Well, I now know that at least the gbp.conf file come straight from `gbp
> clone` without any modification. if new packers will try to find a
> good gbp.conf settings, then looking into existing code will be
> confusing at best. A standard is badly needed, at least a gold example
> that is not too complicated to carry away the gist is the very
> least needed.
Why is it confusing? Didn't you use dh-make-golang to generate a
repository? It should have created the .gbp.conf automatically.

I think that it is fair to say that team standards are dictated by what
dh-make-golang does.

If you create a package with dh-make-golang, it will use pristine-tar
branches. It will also create a .gbp.conf[1], so please don't drop the
pristine-tar branch nor touch the .gbp.conf.

We plan to move to a new layout eventually. However, until then, please
adopt the layout created by dh-make-golang unless you have a good reason
not to.

Anthony explains it clearly on the website (thanks for contributing!):
> dh-make-golang has not yet adapted to this new proposed workflow. For
> newcomers and the less experienced, myself included, it is recommended
> to stick with the old workflow until all the infrastructures
> supporting the migration to the new workflow are in place

1. https://github.com/Debian/dh-make-golang/blob/master/make.go#L588

Cheers,

-- 
Alexandre Viau
aviau at debian.org

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 858 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-go-maintainers/attachments/20180616/b8ae4056/attachment.sig>