-
-
Notifications
You must be signed in to change notification settings - Fork 147
changelog github integration #466
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
Thanks for your pull request, @burner! Bugzilla referencesYour PR doesn't reference any Bugzilla issue. If your PR contains non-trivial changes, please reference a Bugzilla issue or create a manual changelog. Testing this PR locallyIf you don't have a local development environment setup, you can use Digger to test this PR: dub run digger -- build "master + tools#466" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let me know when it's no longer a draft.
@ibuclaw I've taken another look, and I think there is nothing more to do until it fails in prod |
FYI, you could perhaps test this with something like:
Which is what's ran to generate the dlang.org changelog. |
graphql query works mostly bearer not working anymore
next thing to do is wire in the closed github issues even if there where not closed by a commit
now I need to integrate the github issues into the output
513d070
to
00bf95f
Compare
@ibuclaw it should ignore PR's now |
Newlines in issues could either be `\n` or `\r\n`.
When no revision range is given, should instead skip all checking of bugzilla and gitlab.
Prefer to skip checking GitHub when no access token is provided.
Treat the absence of the option as skipping the check for GitHub issues.
Issues closed after the release date should be ignored.
This is sort of better now, thinking this through, my only remaining gripe is that As it stands, it looks like bugs fixed in master-only get wrongly attributed to the current release, when they should be in the next (when master->stable is merged again). Unfortunately this likely means the approach done here is probably wrong, and needs a complete do over. i.e: just scan for |
changed.d
Outdated
struct GitIssues | ||
{ | ||
int[] bugzillaIssueIds; | ||
int[] githubIssueIds; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Here. It looks like these are indeed collected, but then ignored.
|
Issues may be closed by a PR to the master branch, they should not appear as a changelog entry against stable.
This is because each project has a different url path to link to their issues.
This now emits.
Now needs macros defined in |
I think I found the bugzilla one in dlang.org/dlang.org.ddoc but I'm not sure if that is the place to add the (DMD|PHOBOS)GITHUB ones!? |
Isn't bugstitle going to be identical to the bugzilla macro? And for the githubxxx ones, I think first define
|
graphql query works mostly
bearer not working anymore