Closed hannesa2 closed 1 year ago
Btw, please enable issues tab
Thanks!
Unfortunately we can't use the labels at the moment, because we don't want to have public issues. We have a private repo where internal progress is tracked and we could generate release notes there automatically and then copy it to this repo… but this seems cumbersome. If release note generation can process the references to the private repo (like bitfireAT/davx5#123) then it would work.
Do you think this is applicable in our case / without labels from the same repo?
Without labeling they will just run under Other Changes
and are still usefull.
But when this is just a mirror of something private, it will not work.
And there are other ways to organize internal workflows. e.g. ownCloud do it with Projects https://github.com/orgs/owncloud/projects/328/views/1 But this is all your decision.
It's not a mirror, but there are two repos and changes can flow into both directions. We're happy about pull requests in the public repo, but at the moment, that's not a big topic.
I'm closing this for now, but your idea is welcome and we will think about better changelogs!
At least you can use it as a blueprint. Here you can see an example https://github.com/gitx/gitx/releases/tag/0.21