-
Notifications
You must be signed in to change notification settings - Fork 12
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
[Issue #1944] Script to create issues from CLI #1952
base: main
Are you sure you want to change the base?
Conversation
This script allows engineers to create tickets from the CLI and set the value of columns on a project
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.
I still feel like this is overkill 🙂 but at the same time, it does look good to me!
# --project 13 | ||
# --title "New issue title" | ||
# --body "Body of the issue" | ||
# --milestone "<name of milestone>" |
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.
Noting that we aren't using milestones anymore.
# --title "New issue title" | ||
# --body "Body of the issue" | ||
# --milestone "<name of milestone>" | ||
# --deliverable "<name of deliverable (case sensitive)>" |
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.
I believe we are deprecating this as well.
Summary
This script allows engineers to create tickets from the CLI and set the value of columns on a project
Fixes #1944
Time to review: 5 mins
Changes proposed
.github/linters/queries/get-single-select-field.graphql
to query IDs for project fields.github/linters/scripts/create-issue.sh
to create issue and update project fieldsContext for reviewers
Note: The values passed to the following flags are case sensitive and require exact matches to work. The script will fail if they don't match what's in GitHub. Making them case insensitive within the script is a non-trivial effort.
--labels
--deliverable
--track
--status
Additional information
Here's an example issue that was created using the following command executed from within the
.github/linters/
sub-directory