Skip to content

How to delete a branch from the Website repo #6416

Description

@JessicaLucindaCheng

Overview

We need instructions for members of the website-admin team 1 for deleting branches off the Website repo so that we do not have extraneous, unneeded branches.

Action Items

Resources/Instructions

Footnotes

  1. website-admins team ↩

  2. Link to instructions for how to delete a branch from the Website repo: ↩

Activity

  1. JessicaLucindaCheng commented on Mar 10, 2024

    @JessicaLucindaCheng
    Author
  2. github-actions commented on Mar 22, 2024

    @github-actions
  3. JessicaLucindaCheng commented on Mar 23, 2024

    @JessicaLucindaCheng
    Author
  4. 225 remaining items

  5. JessicaLucindaCheng commented on Aug 10, 2026

    @JessicaLucindaCheng
    MemberAuthor

    Update

    • Progress: I still need to write a decision record on why we no longer need instructions for junior devs to delete branches because I changed permissions so website-merge team has explicit access to create a branch. Also, by GitHub's default settings, teams with admin or maintain roles (so for the website repo, website-admins team and website-maintain team respectively) can also create branches, though maintain may need to pass required checks to push.
    • Blockers: None
    • Availability: TBD
    • ETA: TBD

    Tasks & Notes

    • We don't need instructions for how to delete branches for junior devs but should we still have instructions for website-admins team to delete branches created by them or Merge Team members?
      • At the meeting yesterday, we decided that we do need an issue template for deleting branches
      • It would get used by people who wanted to report a branch that needed to be removed, but who don't have admin permission on the repo.
      • It would have the default label role: dev lead
  6. added
    status: UpdatedNo blockers and update is ready for review
    and removed
    status: 2 Weeks InactiveAn issue that has not been updated by an assignee for two weeks
    on Aug 10, 2026
  7. added and removed
    status: UpdatedNo blockers and update is ready for review
    on Aug 14, 2026
  8. hfla-graphql-app commented on Aug 21, 2026

    @hfla-graphql-app
  9. added
    status: 2 Weeks InactiveAn issue that has not been updated by an assignee for two weeks
    and removed on Aug 28, 2026
  10. hfla-graphql-app commented on Aug 28, 2026

    @hfla-graphql-app
  11. hfla-graphql-app commented on Sep 4, 2026

    @hfla-graphql-app
  12. hfla-graphql-app commented on Sep 11, 2026

    @hfla-graphql-app
  13. hfla-graphql-app commented on Sep 18, 2026

    @hfla-graphql-app
  14. hfla-graphql-app commented on Sep 25, 2026

    @hfla-graphql-app
  15. hfla-graphql-app commented on Oct 2, 2026

    @hfla-graphql-app

    Hello @JessicaLucindaCheng-

    Please add an update using the below template (even if you have a pull request). Afterwards, remove
    the status: 2 Weeks Inactive label and add the status: Updated label.

    1. Progress: What is the current status of this issue? What have you completed and what is left to do?
    2. Blockers: Explain any difficulties or errors encountered.
    3. Availability: How much time will you have this week to work on this issue?
    4. ETA: When do you expect this issue to be completed?
    5. Pictures (optional): Add any pictures of the visual changes made to the site so far.

    If you need help, be sure to either: 1) place your issue in the "Questions / In Review" status-column of the
    Project Board and ask for help at your next meeting; 2) put a status: Help Wanted label on your issue
    and pull request; or 3) put up a request for assistance on the team's hfla-site Slack channel.

    Please note that including your questions in the issue comments- along with screenshots, if applicable-
    will help us to help you. Here and here are examples of well-formed questions.

    You are receiving this comment because your last update was before 09/18/2026, 12:07 AM PDT PST.

  16. hfla-graphql-app commented on Oct 9, 2026

    @hfla-graphql-app

    Hello @JessicaLucindaCheng-

    Please add an update using the below template (even if you have a pull request). Afterwards, remove
    the status: 2 Weeks Inactive label and add the status: Updated label.

    1. Progress: What is the current status of this issue? What have you completed and what is left to do?
    2. Blockers: Explain any difficulties or errors encountered.
    3. Availability: How much time will you have this week to work on this issue?
    4. ETA: When do you expect this issue to be completed?
    5. Pictures (optional): Add any pictures of the visual changes made to the site so far.

    If you need help, be sure to either: 1) place your issue in the "Questions / In Review" status-column of the
    Project Board and ask for help at your next meeting; 2) put a status: Help Wanted label on your issue
    and pull request; or 3) put up a request for assistance on the team's hfla-site Slack channel.

    Please note that including your questions in the issue comments- along with screenshots, if applicable-
    will help us to help you. Here and here are examples of well-formed questions.

    You are receiving this comment because your last update was before 09/25/2026, 12:11 AM PDT PST.

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

Metadata

Metadata

Labels

Complexity: SmallTake this type of issues after the successful merge of your second good first issueFeature: AdministrativeAdministrative chores etc.Feature: Wikirole: dev leadsTasks for technical leadssize: 1ptCan be done in 4-6 hoursstatus: 2 Weeks InactiveAn issue that has not been updated by an assignee for two weeks

Type

No type

Projects

Relationships

None yet

Development

No branches or pull requests

Issue actions