[go: nahoru, domu]
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.

Sign up for GitHub

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

Jump to bottom

Adding Labels from cpr command #97

Open
1 task
tomasmrtempe opened this issue Jul 2, 2024 · 2 comments
Open
1 task

Adding Labels from cpr command #97

tomasmrtempe opened this issue Jul 2, 2024 · 2 comments
Labels
kind/feature Changes implying a new feature for the user

Comments

@tomasmrtempe
Copy link

Motivation

Every time we develop new features, we need to set some labels on GitHub web after creating PRs from Sherpa CLI. Then, it would be a very insteresting skill for teams because they would use it from the first moment

Examples:
gh sherpa cpr -i XXXX -labels autodeploy
gh sherpa cpr -i XXXX -labels autopublish/snapshot-binaries

Acceptance criteria

  • Create PR with expected labels assigned automatically.
@tomasmrtempe tomasmrtempe added the kind/feature Changes implying a new feature for the user label Jul 2, 2024
@hielfx
Copy link
Member
hielfx commented Jul 2, 2024

Hi @tomasmrtempe ! Thank you for opening this issue.

We will discuss internally about the implementation of the flag you mention. Currently you can do it with gh pr edit --add-label command after creating the pull request with Sherpa. E.g.:

# Create the pull request with Sherpa
gh sherpa cpr -i XXXX

# Add `autodeploy` and `autopublish/snapshot-binaries` labels to the pull request
gh pr edit --add-label autodeploy,autopublish/snapshot-binaries

Hope this helps you in the mean time.

Thanks!

@tomasmrtempe
Copy link
Author

Hi @hielfx. Thanks for your advice. Bear in mind, if we want to create PRs with autodeploy flag, we'll need a commit after label editing in order to generate snapshot for example,

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/feature Changes implying a new feature for the user
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@hielfx @tomasmrtempe