Manage Collaborators Action

This GitHub action adds and removes multiple users from multiple repositories.

If a user is already part of the repository, running it again with a different permission will change the permission of the user.

A user will be removed from the repository regardless whether the user accepted the invitation. A pending invitation will be cancelled.

Inputs

NAME	DESCRIPTION	TYPE	REQUIRED	DEFAULT
`token`	A GitHub token with admin access to the target repositories	`string`	`true`	`N/A`
`users`	Comma-separated GitHub slug of users to provide access to.	`string`	`true`	`N/A`
`repositories`	Comma-separated GitHub slug of repositories to provide access to (format /<repo_name>).	`string`	`true`	`N/A`
`action`	The action to perform. Add or Remove.	`string`	`true`	`N/A`
`role`	Role of the user in the repository. Only required if action is add.	`string`	`false`	`N/A`

Usage example

Add the following snippet to an existing workflow file

- name: Run Manager Collaborators Action
  id: manager-collaborators-action
  uses: gateixeira/[email protected]
  with:
    token: ${{ secrets.REPO_ACCESS_TOKEN }}
    repositories: owner/repo1,owner/repo2
    users: user1,user2
    role: push
    action: add

The automated release is failing 🚨

🚨 The automated release from the `main` branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the main branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here are some links that can help you:

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

No npm token specified.

An npm token must be created and set in the NPM_TOKEN environment variable on your CI environment.

Please make sure to create an npm token and to set it in the NPM_TOKEN environment variable on your CI environment. The token must allow to publish to the registry https://registry.npmjs.org/.

Good luck with your project ✨

Your semantic-release bot 📦🚀

gateixeira / manage-collaborators-action Goto Github PK