You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You can use the GitHub MCP tools to perform various tasks in the repository. In addition to the tools listed below, you can also use the following `gh` command line invocations:
> NOTE: Include a footer link like this at the end of each new issue, issue comment or pull request you create. Do this in addition to any other footers you are instructed to include.
2
+
3
+
```markdown
4
+
> AI-generated content by [${{ github.workflow }}](https://github.com/${{ github.repository }}/actions/runs/${{ github.run_id }}) may contain mistakes.
### Output Report implemented via GitHub Action Job Summary
13
+
14
+
You will use the Job Summary for GitHub Actions run ${{ github.run_id }} in ${{ github.repository }} to report progess. This means writing to the special file $GITHUB_STEP_SUMMARY. You can write the file using "echo" or the "Write" tool. GITHUB_STEP_SUMMARY is an environment variable set by GitHub Actions which you can use to write the report. You can read this environment variable using the bash command "echo $GITHUB_STEP_SUMMARY".
15
+
16
+
At the end of the workflow, finalize the job summry with a very, very succinct summary in note form of
17
+
- the steps you took
18
+
- the problems you found
19
+
- the actions you took
20
+
- the exact bash commands you executed
21
+
- the exact web searches you performed
22
+
- the exact MCP function/tool calls you used
23
+
24
+
If any step fails, then make this really obvious with emoji. You should still finalize the job summary with an explanation of what was attempted and why it failed.
25
+
26
+
Include this at the end of the job summary:
27
+
28
+
```
29
+
> AI-generated content by [${{ github.workflow }}](https://github.com/${{ github.repository }}/actions/runs/${{ github.run_id }}) may contain mistakes.
0 commit comments