Repo is an Op designed to manage a user's repos on Bitbucket, Gitlab, or Github allowing users to archive, create, delete, and list their repos. This Op will require Gitlab and Github users to access their account through a personal access token while Bitbucket uses a username and password combination. This Op can also be used in Slack allowing users to easily perform these functions without having to navigate to the respective websites.
To run this or any other Op, install the Ops Platform.
Find information about how to run and build Ops via the Ops Platform Documentation.
This Op uses a personal access token for Github and Gitlab authentication. These can be obtained by following the guides below.
The very first time you run this Op, you'll want to set up the appropriate secrets so you don't have to manually enter it in each time.
To set secrets, run:
Follow the prompts and enter in the name of the key and its value. This will save the secret so it can be accessed the next time you use the Op.
This will set the secret to the team which you're currently on (The default is your personal team which is the same as your username). You can also check which team you're currently on by running:
In order to use the secrets you just set, the Op needs to be published to this team.
To run the public version of the Op in the command line, enter in:
ops run @cto.ai/repo
To run the public version of the Op in a public Slack channel:
/ops run cto.ai/repo
1. 👯 Clone the repo:
git clone <git url>
2. 🔨 Navigate into the directory and build the image:
cd repo && ops build .
3. ⚙️ Run the Op from your current working directory with:
ops run .
4. ⚙️ To publish the Op to your team:
ops publish .
To run the Op in Slack, make sure that you have the CTO.ai Bot installed in your Slack workspace.
To run the Op in a Slack channel, enter:
/ops run repo
When submitting issues or requesting help, be sure to also include the version information. To get your Ops version run:
Currently, this Op will not work on accounts with company domains.
Future iterations of this Op can include the ability to create issues, list MRs a user is assigned to, and the list goes on.
See the Contributing Docs for more information.
The following people have contributed to this project: