kpumuk opened a new pull request, #3383:
URL: https://github.com/apache/thrift/pull/3383

   <!-- Explain the changes in the pull request below: -->
   
   This workflow should enable automatic and secure release pipeline for the 
Ruby gem. It is triggered on a new release creation and (temporarily?) on 
manual dispatch action, so that we can force release if there are any changes 
needed for the workflow.
   
   The setup process is described in the official documentation: 
https://guides.rubygems.org/trusted-publishing/#adding-a-trusted-publisher-to-an-existing-gem
   
   The only thing required is to add a trusted publisher on 
[RubyGems.org](https://rubygems.org/gems/thrift):
   
   * Type: GitHub Actions
   * Repository Owner: `apache`
   * Repository Name: `thrift`
   * Workflow Filename: `release_ruby.yml`
   * Environment: `release`
   
   <!-- We recommend you review the checklist/tips before submitting a pull 
request. -->
   
   - [x] Did you create an [Apache 
Jira](https://issues.apache.org/jira/projects/THRIFT/issues/) ticket? 
[THRIFT-5946](https://issues.apache.org/jira/browse/THRIFT-5946)
   - [x] If a ticket exists: Does your pull request title follow the pattern 
"THRIFT-NNNN: describe my issue"?
   - [x] Did you squash your changes to a single commit?  (not required, but 
preferred)
   - [x] Did you do your best to avoid breaking changes?  If one was needed, 
did you label the Jira ticket with "Breaking-Change"?
   - [ ] If your change does not involve any code, include `[skip ci]` anywhere 
in the commit message to free up build resources.
   
   <!--
     The Contributing Guide at:
     https://github.com/apache/thrift/blob/master/CONTRIBUTING.md
     has more details and tips for committing properly.
   -->
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to