Skip to content

chore: mention codeowners when offboarding #751

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.

Sign up for GitHub

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

Merged
milldr merged 2 commits into from
Aug 28, 2025
Merged

chore: mention codeowners when offboarding #751

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
c04eb81
chore(offboarding): mention codeowners
dudymas May 19, 2025
2f72352
Merge branch 'master' into chore/offboarding/add-codeowners
milldr Aug 28, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 7 additions & 2 deletions docs/jumpstart/tutorials/offboarding-cloudposse.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -46,15 +46,20 @@ For things like Okta, Workspaces, or Azure AD:

Typically customers provision a “Cloud Posse” team within their GitHub org.

#### Option 1: Revoke All Access
#### Offboarding Github Access

- Option 1: Revoke All
Revoking this team’s access from repositories should be sufficient to remove all of our access. Also, ensure that any repositories do not have Cloud Posse usernames directly added as external contributors. This happens if repositories were created by our team in your organization.

#### Option 2: Downgrade Access
- Option 2: Downgrade Access
Changing our team’s access to read-only will enable us to still participate in Code Reviews.

<img src="/assets/refarch/cleanshot-2022-02-25-at-17.05.51-20220225-230814.png" /><br/>

#### Offboarding GitHub Ownership

The `CODEOWNERS` file should be checked to make sure that no Cloud Posse usernames or groups are listed. This file is typically located in the root of the repository.

### Spacelift

Depending on how Spacelift was configured, make sure the `LOGIN` policy does not include any Cloud Posse users.
Expand Down
Loading