-
Notifications
You must be signed in to change notification settings - Fork 368
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
create-github-app-token 1.0.0 #4225
create-github-app-token 1.0.0 #4225
Conversation
Don't forget to follow semantic versioning! Breaking changes (including step inputs) should be in major versions only.
|
bash: | ||
entry_file: step.sh | ||
inputs: | ||
- github_repository: null |
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.
As far as I can see in GitHub documentation this input should be in the {owner}/{repo}
format, is it correct? If so it is worth mentioning this in the Step Input's summary or description.
Hi @tdrk18 thanks for the new Step, I left one suggestion, which you might fix in future Step versions, other than that the PR looks good to me! |
Hi @godrei thank you for your review! |
What to do if the build fails?
At the moment contributors do not have access to the CI workflow triggered by StepLib PRs. In case of a failed build, we ask for your patience. Maintainers of Bitrise Steplib will sort it out for you or inform you if any further action is needed.
New Pull Request Checklist
Please mark the points which you did / accept.
bitrise run test
(in the step's repository)bitrise run audit-this-step
(in the step's repository - note, if you don't have this workflow in yourbitrise.yml
, you can copy it from the step template.)New Step
Thank you for the new Step share! The CI check might will fail due to our extended validation engine. Nothing to worry about yet, we will get back to you shortly.