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
Follow-up #3403: Add new option to bundle gem
for choosing a CI service
#3667
Conversation
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.
Looks good!
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.
Looks good, I added a few minor comments.
Regarding the potential discussion, we kind of already had it at #3584. But I feel it becomes a bit too tricky to make all this logic dependent on the --test
logic... 🤔.
bundler/lib/bundler/templates/newgem/.github/workflows/main.yml.tt
Outdated
Show resolved
Hide resolved
bundler/lib/bundler/templates/newgem/.github/workflows/main.yml.tt
Outdated
Show resolved
Hide resolved
I just remembered to also update |
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.
Just some little things I noticed on the Github Actions
configuration.
bundler/lib/bundler/templates/newgem/.github/workflows/main.yml.tt
Outdated
Show resolved
Hide resolved
bundler/lib/bundler/templates/newgem/.github/workflows/main.yml.tt
Outdated
Show resolved
Hide resolved
bundler/lib/bundler/templates/newgem/.github/workflows/main.yml.tt
Outdated
Show resolved
Hide resolved
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.
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.
Found a little issue in the CircleCI
template, and another little issue in the specs that made them not catch the bug in the template.
* `bundle gem` has new option to choose CI provider other than Travis CI
* `bundle gem` has new option to select CI provider
Co-authored-by: Olle Jonsson <olle.jonsson@gmail.com>
* Next version of Bundler will auto choose jobs by default * --retry 3 is already default
* Add hints for --ci option
* https://github.com/ruby/setup-ruby is now the more recommended action
Co-authored-by: David Rodríguez <deivid.rodriguez@riseup.net>
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.
Sounds good, I'll be on standby. Thanks for giving really thorough reviews through this entire PR, it has been very helpful. |
Hi @FTLam11, as you can see from the merge, we ended up doing this in a different order than I had planned, so you no longer need to mess with rebasing this PR :) Just wanted to thank you for your hard work on improving our gem generator 💪. |
Please refer to #3403 for full details. This PR is more of a follow-up and mainly incorporates naming/grammar suggestions while addressing some test suite failures.
One thing that may warrant discussion: Test framework selection/configuration does not currently affect the generation of CI files. So a user can choose to not generate test framework files, while still being able to generate CI files.
Tasks:
I will abide by the code of conduct.