Overview

When departing from a GitHub or Bitbucket organization, it's essential to take certain precautions to protect sensitive data, maintain security, and ensure a smooth transition for the organization and your team members.

Steps To Take Before Leaving

Here are important steps to consider before leaving a GitHub or Bitbucket organization:

1. Remove SSH/API Keys from Configurations

Before your departure, ensure that all your SSH keys, API tokens, or other credentials associated with your account are removed from configuration files and repositories. This step helps prevent unauthorized access to repositories and sensitive data. Follow these actions:

1. Review configuration files in repositories for any stored keys or tokens.
2. Replace personal keys with shared or organizational authentication methods.
3. Invalidate and revoke any personal access tokens or keys to prevent future unauthorized access.

2. Unfollow Projects and Repositories

To maintain clarity and streamline notifications for both yourself and the organization, unfollowing repositories and projects is beneficial. By unfollowing, you will no longer receive notifications related to activities within those repositories. Take these steps:

1. Visit the repositories and projects you are currently following.
2. Unfollow repositories to stop receiving notifications for activities within those repositories.
3. Ensure that you are not subscribed to any unnecessary notifications or alerts.

3. Communicate Changes to Team Members

Inform your team members and collaborators about your departure and the steps you have taken to secure access and configurations. Seek to ensure that everyone is aware of the necessary actions to maintain security and operational continuity post-departure.

Additional Resources

• How Do I Stop Getting Build Notification Emails For Projects?
• Removing Unwanted Organizations from Drop-down Menu