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.

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

Setup Github actions for use in SQM projects #2

Merged
merged 1 commit into from
Sep 4, 2024

Conversation

dmhuff
Copy link
Collaborator

@dmhuff dmhuff commented Sep 4, 2024

This replaces the Github actions used by the official Bootstrap repo with ones that allow us to maintain and publish the gem in the SQM package repo. The actions are the same as the ones we use for our own gems, with the following small differences:

  1. Bootstrap uses "main" instead of "master" for its release branch.
  2. Using Bootstrap's Rake task for building the gem.
  3. Releasing the packaged gem from the pkg directory.

This should ensure that the modified gem that we use is a close as possible to the official Bootstrap release.

This also updates the gem's version number, combining the minor and point release numbers as the minor number and using the point release number to designate the custom SQM version (e.g. "5.3.3" becomes "5.33.1"). This is done because the version-forget-me-not Github action can only support semantic versioning with three numbers.

1207966452799142

This replaces the Github actions used by the official Bootstrap repo
with ones that allow us to maintain and publish the gem in the SQM
package repo. The actions are the same as the ones we use for our own
gems, with the following small differences:

1. Bootstrap uses "main" instead of "master" for its release branch.
2. Using Bootstrap's Rake task for building the gem.
3. Releasing the packaged gem from the `pkg` directory.

This should ensure that the modified gem that we use is a close as
possible to the official Bootstrap release.

This also updates the gem's version number, combining the minor and
point release numbers as the minor number and using the point release
number to designate the custom SQM version (e.g. "5.3.3" becomes
"5.33.1"). This is done because the version-forget-me-not Github action
can only support semantic versioning with three numbers.

[1207966452799142](https://app.asana.com/0/0/1207966452799142/f)
@dmhuff dmhuff force-pushed the 1207966452799142-upgrade-to-bootstrap-5 branch from 374d929 to f502a78 Compare September 4, 2024 14:21
@nspielman nspielman merged commit 9b5c5fd into main Sep 4, 2024
2 checks passed
@dmhuff dmhuff deleted the 1207966452799142-upgrade-to-bootstrap-5 branch September 4, 2024 14:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants