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

chore(rotation): Change "Usage" heading in README to all caps #1180

Merged
merged 4 commits into from
Dec 13, 2023

Conversation

JGibson2019
Copy link
Contributor

@JGibson2019 JGibson2019 commented Dec 13, 2023

Details

This is updating the text in the README for the Usage section to now show "USAGE".

Motivation

Triggering a build to confirm that the new GH token is being consumed properly

Context

Quarterly DRI rotation

Pull request checklist

  • PR title respects Conventional Commits (starts with fix:, feat:, etc, and is suitable for user-facing release notes)
  • PR contains no breaking changes, OR description of both PR and final merge commit starts with BREAKING CHANGE:
  • (if applicable) Addresses issue: #0000
  • Added relevant unit tests for your changes
  • Ran yarn precheckin
  • Verified code coverage for the changes made

@JGibson2019 JGibson2019 requested a review from a team as a code owner December 13, 2023 00:00
Removing space after USAGE so that formatting rules respected
Copy link
Contributor

@peterdur peterdur left a comment

Choose a reason for hiding this comment

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

Approved readme touch

@codeofdusk codeofdusk changed the title Update README.md trivially to see if I can trigger a CI build fix: Change "Usage" heading in README to all caps Dec 13, 2023
@JGibson2019 JGibson2019 merged commit 0da328e into main Dec 13, 2023
2 checks passed
@JGibson2019 JGibson2019 changed the title fix: Change "Usage" heading in README to all caps chore(rotation): Change "Usage" heading in README to all caps Dec 13, 2023
JGibson2019 added a commit that referenced this pull request Dec 13, 2023
Returning back to standard format after trivial change in #1180
codeofdusk pushed a commit that referenced this pull request Dec 24, 2023
…ivial change (#1181)

This commit returns back to standard format after trivial change in #1180. "USAGE"
is now back to "Usage". Will sync with vendor team to see how migration
is affecting token consumption.

Part of quarterly rotation
@ada-cat
Copy link
Collaborator

ada-cat commented Mar 28, 2024

🎉 This PR is included in version 2.11.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants