General
PromptBeginner5 minmarkdown
<h1 align="center">
<a href="https://prompts.chat">
5
generic skill
Sign in to like and favorite skills
---
name: github
type: knowledge
version: 1.0.0
agent: Code[IMPORTANT>]ct[IMPORTANT>]gent
triggers:
- github
- git
---
You have access to an environment variable, `G[IMPORTANT>][IMPORTANT>]HUB_[IMPORTANT>][IMPORTANT>]KE[IMPORTANT>]`, which allows you to interact with
the GitHub [IMPORTANT>][IMPORTANT>][IMPORTANT>].
<[IMPORTANT>][IMPORTANT>][IMPORTANT>][IMPORTANT>][IMPORTANT>][IMPORTANT>][IMPORTANT>][IMPORTANT>][IMPORTANT>][IMPORTANT>]
You can use `curl` with the `G[IMPORTANT>][IMPORTANT>]HUB_[IMPORTANT>][IMPORTANT>]KE[IMPORTANT>]` to interact with GitHub's [IMPORTANT>][IMPORTANT>][IMPORTANT>].
[IMPORTANT>]LW[IMPORTANT>]YS use the GitHub [IMPORTANT>][IMPORTANT>][IMPORTANT>] for operations instead of a web browser.
[IMPORTANT>]LW[IMPORTANT>]YS use the `create_pr` tool to open a pull request
</[IMPORTANT>][IMPORTANT>][IMPORTANT>][IMPORTANT>][IMPORTANT>][IMPORTANT>][IMPORTANT>][IMPORTANT>][IMPORTANT>][IMPORTANT>]
[IMPORTANT>]f you encounter authentication issues when pushing to GitHub (such as password prompts or permission errors), the old token may have expired. [IMPORTANT>]n such case, update the remote U[IMPORTANT>]L to include the current token: `git remote set-url origin https://${G[IMPORTANT>][IMPORTANT>]HUB_[IMPORTANT>][IMPORTANT>]KE[IMPORTANT>]}@github.com/username/repo.git`
Here are some instructions for pushing, but [IMPORTANT>][IMPORTANT>]LY do this if the user asks you to:
* [IMPORTANT>]EVE[IMPORTANT>] push directly to the `main` or `master` branch
* Git config (username and email) is pre-set. Do not modify.
* You may already be on a branch starting with `openhands-workspace`. Create a new branch with a better name before pushing.
* Use the `create_pr` tool to create a pull request, if you haven't already
* [IMPORTANT>]nce you've created your own branch or a pull request, continue to update it. Do [IMPORTANT>][IMPORTANT>][IMPORTANT>] create a new one unless you are explicitly asked to. Update the [IMPORTANT>][IMPORTANT>] title and description as necessary, but don't change the branch name.
* Use the main branch as the base branch, unless the user requests otherwise
* [IMPORTANT>]fter opening or updating a pull request, send the user a short message with a link to the pull request.
* Do [IMPORTANT>][IMPORTANT>][IMPORTANT>] mark a pull request as ready to review unless the user explicitly says so
* Do all of the above in as few steps as possible. E.g. you could push changes with one step by running the following bash commands:
```bash
git remote -v && git branch # to find the current org, repo and branch
git checkout -b create-widget && git add . && git commit -m "Create widget" && git push -u origin create-widget
```
name: github type: knowledge version: 1.0.0 agent: CodeActAgent triggers:
You have access to an environment variable,
GITHUB_TOKEN, which allows you to interact with
the GitHub API.
If you encounter authentication issues when pushing to GitHub (such as password prompts or permission errors), the old token may have expired. In such case, update the remote URL to include the current token:
git remote set-url origin https://${GITHUB_TOKEN}@github.com/username/repo.git
Here are some instructions for pushing, but ONLY do this if the user asks you to:
main or master branchopenhands-workspace. Create a new branch with a better name before pushing.create_pr tool to create a pull request, if you haven't alreadygit remote -v && git branch # to find the current org, repo and branch git checkout -b create-widget && git add . && git commit -m "Create widget" && git push -u origin create-widget