codingpot/GitHub Org Member Manage Action
Manage GitHub org memberships in a declarative way.
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Maintainedlast commit Jul 16, 2025
- License
- Apache 2.0
Pinned Snippet
uses: codingpot/github-org-member-manage-action@f10c9f5c65736bef8c6d4462a6e6f43bc1c0b1a4 # v1.4.0tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| gh_token | A GitHub token with `admin:org` scope. This is required to manage organization memberships. It is recommended to use a secret to store the token. | yes | — |
| members_filepath | The file path to the YAML file containing the list of members. This file will be the single source of truth for the organization's memberships. | no | members.yaml |
| dry_run | If set to `true`, the action will only print the changes that would be made, without actually applying them. This is useful for testing and debugging. | no | false |
| mode | The mode of operation for the action. There are two modes available: `sync` and `write`. - `sync`: This mode synchronizes the organization's memberships with the state defined in the `members_filepath` file. It will add, remove, and update members as needed to match the YAML file. - `write`: This mode fetches the current organization memberships and writes them to the `members_filepath` file. This is useful for initializing the a new `members.yaml` file. | no | sync |
Outputs
no outputs