.github/ISSUE_TEMPLATE/bug.yml

@@ -0,0 +1,41 @@
+name: Bug
+description: File a bug report
+title: "[BUG]: "
+labels: ["Type: Bug", "Status: Triage"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for taking the time to fill out this bug report!
+  - type: textarea
+    id: what-happened
+    attributes:
+      label: What happened?
+      description: What did you do? What happened? What did you expect to happen?
+      placeholder: Put your description of the bug here.
+    validations:
+      required: true
+  - type: textarea
+    id: versions
+    attributes:
+      label: Versions
+      description: What versions of the relevant software are you running?
+      placeholder: Octokit.js v2.0.10, Node v16.18.0
+    validations:
+      required: true
+  - type: textarea
+    id: logs
+    attributes:
+      label: Relevant log output
+      description: |
+        Please copy and paste any relevant log output. This will be automatically formatted into code, so no need for backticks.
+        Please check your logs before submission to ensure sensitive information is redacted.
+      render: shell
+  - type: checkboxes
+    id: terms
+    attributes:
+      label: Code of Conduct
+      description: By submitting this issue, you agree to follow our [Code of Conduct](CODE_OF_CONDUCT.md)
+      options:
+        - label: I agree to follow this project's Code of Conduct
+          required: true

.github/ISSUE_TEMPLATE/documentation.yml

@@ -0,0 +1,49 @@
+name: Documentation
+description: Update or add documentation
+title: "[DOCS]: "
+labels: ["Type: Documentation", "Status: Triage"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for taking the time to fill this out!
+  - type: textarea
+    id: describe-need
+    attributes:
+      label: Describe the need
+      description: What do you wish was different about our docs?
+      placeholder: Describe the need for documentation updates here.
+    validations:
+      required: true
+  - type: input
+    id: sdk_version
+    attributes:
+      label: SDK Version
+      description: Do these docs apply to a specific SDK version?
+      placeholder: Octokit.NET v4.0.1
+    validations:
+      required: false
+  - type: input
+    id: api_version
+    attributes:
+      label: API Version
+      description: Do these docs apply to a specific version of the GitHub REST API or GraphQL API?
+      placeholder: ex. v1.1.1
+    validations:
+      required: false
+  - type: textarea
+    id: logs
+    attributes:
+      label: Relevant log output
+      description: |
+        Please copy and paste any relevant log output. This will be automatically formatted into code, so no need for backticks.
+        Please check your logs before submission to ensure sensitive information is redacted.
+      render: shell
+  - type: checkboxes
+    id: terms
+    attributes:
+      label: Code of Conduct
+      description: By submitting this issue, you agree to follow our [Code of Conduct](CODE_OF_CONDUCT.md)
+      options:
+        - label: I agree to follow this project's Code of Conduct
+          required: true

.github/ISSUE_TEMPLATE/feature.yml

@@ -0,0 +1,49 @@
+name: Feature
+description: Suggest an idea for a new feature or enhancement
+title: "[FEAT]: "
+labels: ["Type: Feature", "Status: Triage"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for taking the time to fill this out!
+  - type: textarea
+    id: describe-need
+    attributes:
+      label: Describe the need
+      description: What do you want to happen? What problem are you trying to solve?
+      placeholder: Describe the need for the feature.
+    validations:
+      required: true
+  - type: input
+    id: sdk_version
+    attributes:
+      label: SDK Version
+      description: Does this feature suggestion apply to a specific SDK version?
+      placeholder: Octokit.rb v6.0.0
+    validations:
+      required: false
+  - type: input
+    id: api_version
+    attributes:
+      label: API Version
+      description: Does this feature suggestion apply to a specific version of the GitHub REST API or GraphQL API?
+      placeholder: ex. v1.1.1
+    validations:
+      required: false
+  - type: textarea
+    id: logs
+    attributes:
+      label: Relevant log output
+      description: |
+        Please copy and paste any relevant log output. This will be automatically formatted into code, so no need for backticks.
+        Please check your logs before submission to ensure sensitive information is redacted.
+      render: shell
+  - type: checkboxes
+    id: terms
+    attributes:
+      label: Code of Conduct
+      description: By submitting this issue, you agree to follow our [Code of Conduct](CODE_OF_CONDUCT.md)
+      options:
+        - label: I agree to follow this project's Code of Conduct
+          required: true

.github/ISSUE_TEMPLATE/maintenance.yml

@@ -0,0 +1,49 @@
+name: Maintenance
+description: Dependencies, cleanup, refactoring, reworking of code
+title: "[MAINT]: "
+labels: ["Type: Maintenance", "Status: Triage"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for taking the time to fill this out!
+  - type: textarea
+    id: describe-need
+    attributes:
+      label: Describe the need
+      description: What do you want to happen?
+      placeholder: Describe the maintenance need here.
+    validations:
+      required: true
+  - type: input
+    id: sdk_version
+    attributes:
+      label: SDK Version
+      description: Does this maintenance apply to a specific SDK version?
+      placeholder: terraform-provider-github v5.7.0
+    validations:
+      required: false
+  - type: input
+    id: api_version
+    attributes:
+      label: API Version
+      description: Does this maintenance apply to a specific version of the GitHub REST API or GraphQL API?
+      placeholder: ex. v1.1.1
+    validations:
+      required: false
+  - type: textarea
+    id: logs
+    attributes:
+      label: Relevant log output
+      description: |
+        Please copy and paste any relevant log output. This will be automatically formatted into code, so no need for backticks.
+        Please check your logs before submission to ensure sensitive information is redacted.
+      render: shell
+  - type: checkboxes
+    id: terms
+    attributes:
+      label: Code of Conduct
+      description: By submitting this issue, you agree to follow our [Code of Conduct](CODE_OF_CONDUCT.md)
+      options:
+        - label: I agree to follow this project's Code of Conduct
+          required: true

.github/pull_request_template.md

@@ -0,0 +1,61 @@
+<!-- Please refer to our contributing docs for any questions on submitting a pull request -->
+
+
+<!-- Issues are required for both bug fixes and features. -->
+Resolves #ISSUE_NUMBER
+
+----
+
+## Behavior
+
+### Before the change?
+<!-- Please describe the current behavior that you are modifying. -->
+
+*
+
+### After the change?
+<!-- Please describe the behavior or changes that are being added by this PR. -->
+
+*
+
+
+### Other information
+<!-- Any other information that is important to this PR  -->
+
+*
+
+----
+
+## Additional info
+
+### Pull request checklist
+- [ ] Tests for the changes have been added (for bug fixes / features)
+- [ ] Docs have been reviewed and added / updated if needed (for bug fixes / features)
+- [ ] Added the appropriate label for the given change
+
+### Does this introduce a breaking change?
+<!-- If this introduces a breaking change make sure to note it here any what the impact might be -->
+
+Please see our docs on [breaking changes](https://github.com/octokit/.github/blob/main/community/breaking_changes.md) to help!
+
+- [ ] Yes (Please add the `Type: Breaking change` label)
+- [ ] No
+
+If `Yes`, what's the impact:
+
+* N/A
+
+
+### Pull request type
+
+<!-- Please do not submit updates to dependencies unless it fixes an issue. -->
+<!-- Please try to limit your pull request to one type, submit multiple pull requests if needed. -->
+
+Please add the corresponding label for change this PR introduces:
+- Bugfix: `Type: Bug`
+- Feature/model/API additions: `Type: Feature`
+- Updates to docs or samples: `Type: Documentation`
+- Dependencies/code cleanup: `Type: Maintenance`
+
+----
+

.github/workflows/add_to_octokit_project.yml

@@ -0,0 +1,20 @@
+name: Add PRs and issues to Octokit org project
+
+on:
+  issues:
+    types: [reopened, opened]
+  pull_request_target:
+    types: [reopened, opened]
+
+jobs:
+  add-to-project:
+    name: Add issue to project
+    runs-on: ubuntu-latest
+    continue-on-error: true
+    steps:
+      - uses: actions/add-to-project@v0.4.0
+        with:
+          project-url: https://github.com/orgs/octokit/projects/10
+          github-token: ${{ secrets.OCTOKITBOT_PROJECT_ACTION_TOKEN }}
+          labeled: "Status: Stale"
+          label-operator: NOT

.github/workflows/release.yml

@@ -1,7 +1,7 @@
 "on":
   push:
     branches:
-      - master
+      - main
       - next
       - beta
       - "*.x"
@@ -14,7 +14,7 @@ jobs:
       - uses: actions/checkout@v3
       - uses: actions/setup-node@v3
         with:
-          node-version: 16
+          node-version: lts/*
           cache: npm
       - run: npm ci
       - run: npm run build

.github/workflows/test.yml

@@ -2,7 +2,7 @@ name: Test
 "on":
   push:
     branches:
-      - master
+      - main
       - next
       - beta
       - dependabot/npm_and_yarn/**

.github/workflows/update-docs.yml

@@ -1,8 +1,8 @@
-name: Update docs on pushes to master
+name: Update docs on pushes to main
 "on":
   push:
     branches:
-      - master
+      - main
 jobs:
   update_docs:
     runs-on: ubuntu-latest

CONTRIBUTING.md

@@ -48,14 +48,14 @@ variable (or set it in a `.env` file) to avoid running against GitHub's rate lim
 
 Here is an overview of [how `@octokit/rest` works](HOW_IT_WORKS.md).
 
-- Create a topic branch from the master branch.
+- Create a topic branch from the main branch.
 - Check for unnecessary whitespace / changes with `git diff --check` before committing.
 - Keep git commit messages clear and appropriate. Ideally follow commit conventions described below.
 
 ## Submitting the Pull Request
 
 - Push your changes to your topic branch on your fork of the repo.
-- Submit a pull request from your topic branch to the master branch on the `rest.js` repository.
+- Submit a pull request from your topic branch to the main branch on the `rest.js` repository.
 - Be sure to tag any issues your pull request is taking care of / contributing to. \* Adding "Closes #123" to a pull request description will auto close the issue once the pull request is merged in.
 
 ## Testing a pull request from github repo locally: