Heptapod CI: stop triggering HGitaly downstream builds in hgitaly2 branch
We won't need to create a hgitaly2 branch in HGitaly, because the changes are mostly new RPC services, and refactors can be made safely (especially with native projects still considered experimental). On the other hand we needed one in py-heptapod because we're impacting potentially all Mercurial projects. No downstream HGitaly pipeline is configured to work on the hgitaly2 branch of py-heptapod, so it doesn't make sense to trigger anything.
parent
8a30e3ed
No related branches found
No related tags found
Loading
Please register or sign in to comment