-
Notifications
You must be signed in to change notification settings - Fork 278
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
Proposal for a job/webpage to create issue across all repos. #3349
Comments
I don't recommend web pages. This requires tokens and what not. However, we could probably use tooling to create campaigns. It could be a bot that's installed in the org and we could take an issue, add |
This can be confined to Github workflow and can be run in individual repos. |
This can be done by creating a github action and having a workflow using this GH action, this workflow will have inputs same as described above and can be part of each repo. So when this workflow is triggered from the repo the meta/campaign/issue is created from that source repo and across other repos. |
Closing this issue as the Component release issues are auto-created along with the main release issue part of the build repo. |
Is your feature request related to a problem? Please describe
Today we use a combination of
meta
andgh
cli to create issues out of a template across all the repos, this has its own challenges for the workspace setup on the local, following a series of steps , but now and then a developer/release-manager have to spend some time to create issues/campaigns across multiple repos, this also include writing the template and setting up themeta
andgh
environment.Describe the solution you'd like
A job/webpage to create issue across all repos that looks as follows
The job/webpage/tool can have 3 conditions.
Describe alternatives you've considered
No response
Additional context
This is just a proposal setup and would save lot of time for a release manager or in general for a user who want to create multiple campaigns and stories/issues across all the repos. If this is an overkill and have something better and simpler other than configuring
meta
gh
with issue template (a .MD file), open for suggestions and can close this issue :)The text was updated successfully, but these errors were encountered: