Skip to content

Commit f81f279

Browse files
committed
Merge branch 'main' of https://github.com/akenneth/github-mcp-server into list-issue-types
2 parents a5906d6 + 02c8629 commit f81f279

File tree

88 files changed

+7851
-855
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

88 files changed

+7851
-855
lines changed
Lines changed: 28 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,28 @@
1+
name: Close inactive issues
2+
on:
3+
schedule:
4+
- cron: "30 8 * * *"
5+
6+
jobs:
7+
close-issues:
8+
runs-on: ubuntu-latest
9+
env:
10+
PR_DAYS_BEFORE_STALE: 60
11+
PR_DAYS_BEFORE_CLOSE: 10
12+
PR_STALE_LABEL: stale
13+
permissions:
14+
issues: write
15+
pull-requests: write
16+
steps:
17+
- uses: actions/stale@v9
18+
with:
19+
days-before-issue-stale: ${{ env.PR_DAYS_BEFORE_STALE }}
20+
days-before-issue-close: ${{ env.PR_DAYS_BEFORE_CLOSE }}
21+
stale-issue-label: ${{ env.PR_STALE_LABEL }}
22+
stale-issue-message: "This issue is stale because it has been open for ${{ env.PR_DAYS_BEFORE_STALE }} days with no activity. Leave a comment to avoid closing this issue in ${{ env.PR_DAYS_BEFORE_CLOSE }} days."
23+
close-issue-message: "This issue was closed because it has been inactive for ${{ env.PR_DAYS_BEFORE_CLOSE }} days since being marked as stale."
24+
days-before-pr-stale: -1
25+
days-before-pr-close: -1
26+
# Start with the oldest items first
27+
ascending: true
28+
repo-token: ${{ secrets.GITHUB_TOKEN }}

.github/workflows/go.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ jobs:
2626
run: go mod download
2727

2828
- name: Run unit tests
29-
run: go test -race ./...
29+
run: script/test
3030

3131
- name: Build
3232
run: go build -v ./cmd/github-mcp-server

.gitignore

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -12,3 +12,6 @@ __debug_bin*
1212
# Go
1313
vendor
1414
bin/
15+
16+
# macOS
17+
.DS_Store

CONTRIBUTING.md

Lines changed: 22 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -10,24 +10,36 @@ Contributions to this project are [released](https://help.github.com/articles/gi
1010

1111
Please note that this project is released with a [Contributor Code of Conduct](CODE_OF_CONDUCT.md). By participating in this project you agree to abide by its terms.
1212

13+
## What we're looking for
14+
15+
We can't guarantee that every tool, feature, or pull request will be approved or merged. Our focus is on supporting high-quality, high-impact capabilities that advance agentic workflows and deliver clear value to developers.
16+
17+
To increase the chances your request is accepted:
18+
* Include real use cases or examples that demonstrate practical value
19+
* If your request stalls, you can open a Discussion post and link to your issue or PR
20+
* We actively revisit requests that gain strong community engagement (👍s, comments, or evidence of real-world use)
21+
22+
Thanks for contributing and for helping us build toolsets that are truly valuable!
23+
1324
## Prerequisites for running and testing code
1425

1526
These are one time installations required to be able to test your changes locally as part of the pull request (PR) submission process.
1627

17-
1. install Go [through download](https://go.dev/doc/install) | [through Homebrew](https://formulae.brew.sh/formula/go)
18-
1. [install golangci-lint v2](https://golangci-lint.run/welcome/install/#local-installation)
28+
1. Install Go [through download](https://go.dev/doc/install) | [through Homebrew](https://formulae.brew.sh/formula/go)
29+
2. [Install golangci-lint v2](https://golangci-lint.run/welcome/install/#local-installation)
1930

2031
## Submitting a pull request
2132

22-
> **Important**: Please open your pull request against the `next` branch, not `main`. The `next` branch is where we integrate new features and changes before they are merged to `main`.
23-
2433
1. [Fork][fork] and clone the repository
25-
1. Make sure the tests pass on your machine: `go test -v ./...`
26-
1. Make sure linter passes on your machine: `golangci-lint run`
27-
1. Create a new branch: `git checkout -b my-branch-name`
28-
1. Make your change, add tests, and make sure the tests and linter still pass
29-
1. Push to your fork and [submit a pull request][pr] targeting the `next` branch
30-
1. Pat yourself on the back and wait for your pull request to be reviewed and merged.
34+
2. Make sure the tests pass on your machine: `go test -v ./...`
35+
3. Make sure linter passes on your machine: `golangci-lint run`
36+
4. Create a new branch: `git checkout -b my-branch-name`
37+
5. Add your changes and tests, and make sure the Action workflows still pass
38+
- Run linter: `script/lint`
39+
- Update snapshots and run tests: `UPDATE_TOOLSNAPS=true go test ./...`
40+
- Update readme documentation: `script/generate-docs`
41+
6. Push to your fork and [submit a pull request][pr] targeting the `main` branch
42+
7. Pat yourself on the back and wait for your pull request to be reviewed and merged.
3143

3244
Here are a few things you can do that will increase the likelihood of your pull request being accepted:
3345

0 commit comments

Comments
 (0)