Skip to content

Add follow-up step to add member playbook #54

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
merged 1 commit into from
Oct 2, 2024
Merged

Add follow-up step to add member playbook #54

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
7 changes: 7 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -40,6 +40,13 @@ Django Commons packages.
5. Create a pull-request to `main` branch. This will trigger terraform to plan the changes in the organization to be
executed. Review the changes and make sure they align with the request.
6. Merge the pull request. This will trigger terraform to apply the changes in the organization.
7. Comment on the issue, thanking the person for joining and reminding them that it helps the
organization's reach if they set their membership visibility as public.

> Thank you <NAME> for joining! You'll get an invite email from GitHub. You'll have one
> week to accept that. If you don't mind, after accepting, can you set your
> [organization membership as public](https://github.com/orgs/django-commons/people)?
> This helps Django Commons grow.

## Repository Team Change Playbook

Expand Down