Skip to content

Update GitHub Actions best practices: use OSBotify token as little as possible #31571

Closed

Description

@roryabraham

Problem

Using OSBotify token requires repo secrets and extra steps. Sometimes it's necessary, such as when committing or pushing code in our CI.

Solution

Precisely nail down the scenarios when OSBotify is needed. When he's not, use the standard github.token instead.

Activity

  1. self-assigned this
    on Nov 20, 2023
  2. roryabraham commented on Nov 21, 2023

    @roryabraham
    ContributorAuthor

    Stopped using it for checklists, and that's a start. But there's a lot of usages currently.

    Another example when the GitHub Actions token doesn't work is when accessing stuff at the org level like GitHub teams

  3. roryabraham commented on Dec 1, 2023

    @roryabraham
    ContributorAuthor

    No update, lower priority item

  4. roryabraham commented on Dec 11, 2023

    @roryabraham
    ContributorAuthor

    Created one PR to help move this in the right direction and eliminate a source of flakiness: #32848

  5. roryabraham commented on Dec 20, 2023

    @roryabraham
    ContributorAuthor

    No update, have been OOO

  6. roryabraham commented on Dec 29, 2023

    @roryabraham
    ContributorAuthor

    No update here

  7. roryabraham commented on Jan 9, 2024

    @roryabraham
    ContributorAuthor

    No update

  8. roryabraham commented on Jan 17, 2024

    @roryabraham
    ContributorAuthor

    Going to close this since we haven't been seeing nearly as many stability issues with the OSBotify bot token

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions