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

fix: update collections-renames.yml to use the correct action permissions #4508

Merged
merged 1 commit into from
Nov 4, 2024

Conversation

jmeridth
Copy link
Member

@jmeridth jmeridth commented Nov 4, 2024

Please confirm this pull request meets the following requirements:

Which change are you proposing?

  • Suggesting edits to an existing topic or collection
  • Curating a new topic or collection
  • Something that does not neatly fit into the binary options above

Editing an existing topic or collection

I'm suggesting these edits to an existing topic or collection:

  • Image (and my file is *.png, square, dimensions 288x288, size <= 75 kB)
  • Content (and my changes are in index.md)

Please replace this line with an explanation of why you think these changes should be made.

Curating a new topic or collection

  • I've formatted my changes as a new folder directory, named for the topic or collection as it appears in the URL on GitHub (e.g. https://github.com/topics/[NAME] or https://github.com/collections/[NAME])
  • My folder contains a *.png image (if applicable) and index.md
  • All required fields in my index.md conform to the Style Guide and API docs: https://github.com/github/explore/tree/main/docs

Please replace this line with an explanation of why you think this topic or collection should be curated.

Something that does not neatly fit into the binary options above

  • My suggested edits are not about an existing topic or collection, or at least not a single one
  • My suggested edits are not about curating a new topic or collection, or at least not a single one
  • My suggested edits conform to the Style Guide and API docs: https://github.com/github/explore/tree/main/docs

collections-renames.yml workflow runs have been failing since 10/20/2024. This will fix that.

  • add farady-retry gem to Gemfile to solve warning in server run

Please note: we will close your PR without comment if you do not check the boxes above and provide ALL requested information.

…ions

- [x] add farady-retry gem to Gemfile to solve warning in server run

Signed-off-by: Jason Meridth <[email protected]>
@jmeridth jmeridth self-assigned this Nov 4, 2024
@jmeridth jmeridth requested a review from a team as a code owner November 4, 2024 03:58
@jmeridth
Copy link
Member Author

jmeridth commented Nov 4, 2024

Expected failure. Merging to kick off cron that will create PR.

@jmeridth jmeridth merged commit b8f7b45 into main Nov 4, 2024
7 of 8 checks passed
@jmeridth jmeridth deleted the jm_fix_collections_action_permissions branch November 4, 2024 04:02
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.

1 participant