Skip to content

Conversation

@ShimShtein
Copy link
Member

  • Added a general RELEASE.md file to document the process
  • Added a github action that will build and publish the gem on new tag

* Added a general `RELEASE.md` file to document the process
* Added a github action that will build and publish the gem on new tag

### Note on permissions

The steps outlined above require write access to the repository. If needed, steps 1-4 can be done even without permissions. In that case, skip step 5, push the changes to your own fork and send us a pull request, asking for a maintainer to perform step 5.
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ekohl I have removed the link to a team, since no team seem relevant to this plugin. Maybe we should think about adding this plugin to at least some team?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes we should. Not sure who would be in that team though.

@ekohl ekohl merged commit 9f6f95d into theforeman:master Dec 23, 2025
2 of 3 checks passed
@ekohl
Copy link
Member

ekohl commented Dec 23, 2025

I've touched up the commit to follow https://cbea.ms/git-commit/#imperative and set up the trusted publisher.

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