Skip to content
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

Enhancement - Auto label PRs and issues with a fix version? #2

Open
jaikiran opened this issue Aug 21, 2020 · 1 comment
Open

Enhancement - Auto label PRs and issues with a fix version? #2

jaikiran opened this issue Aug 21, 2020 · 1 comment

Comments

@jaikiran
Copy link

jaikiran commented Aug 21, 2020

In context of oracle/graal#2764 (comment) would it be possible to automate this through this issuelabeler project? Whenever a PR gets merged perhaps look for a specific file within the repo to know the "next release version" and use that value to set the Milestone of that merged PR to this value? If setting the milestone isn't doable then perhaps add a "Fix version: the-version" kind of label? If this works, then maybe it can even be extended to do this same thing on issues that get closed when the corresponding PR is closed?

Of course, someone will have to maintain that file containing the "next project version" and ensure that on every release it is up to date. Perhaps allow the file to be configurable and some regex that determines how to "find" a version in that file, so that existing project artifacts (like a pom.xml or in case of mx builds their equivalent file) can be used to infer the version?

P.S: I've no idea if this is even in the scope of this project, but I thought I'll just go ahead and ask :)

@maxandersen
Copy link
Owner

sorry, completely missed this one - what you write is definitely possible; but we would need to consider put that in a separate flow/script - but yes, very doable.

about "marker" for what is "next" I would instead of a text file consider if just fetching last N milestones and pick the one that has "[NEXT]" or similar 'tag' in the description.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants