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
Use a workflow similar to this one to regenerate Insomnia routes whenever a new octokit/routes release becomes available:
name: Update REST API endpoint methodson:
repository_dispatch:
types: [octokit-routes-release]jobs:
update_routes:
runs-on: ubuntu-lateststeps:
- uses: actions/checkout@master
- uses: actions/setup-node@v1with:
node-version: "12.x"# try checking out routes-update branch. Ignore error if it does not exist
- run: git checkout routes-update || true
- run: npm ci
- run: npm run update-endpointsenv:
VERSION: ${{ github.event.client_payload.version }}
- name: Create Pull Requestuses: gr2m/create-or-update-pull-request-action@v1.xenv:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}with:
title: "🚧 GitHub REST Endpoints changed"body: | See what changed at https://github.com/octokit/routes/releases/latest. Make sure to update the commits so that the merge results in helpful release notes, see [Merging the Pull Request & releasing a new version](https://github.com/octokit/rest.js/blob/master/CONTRIBUTING.md#merging-the-pull-request--releasing-a-new-version). In general - Avoid breaking changes at all costs - If there are no typescript or code changes, use a `docs` prefix - If there are typescript changes but no code changes, use `fix(typescript)` prefix - If there are code changes, use `fix` if a problem was resolved, `feat` if new endpoints / parameters were added, and `feat(deprecation)` if a method was deprecated.branch: "routes-update"commit-message: "WIP octokit/routes updated"author: "Octokit Bot <33075676+octokitbot@users.noreply.github.com>"
Use a workflow similar to this one to regenerate Insomnia routes whenever a new octokit/routes release becomes available:
Inspiration.
The text was updated successfully, but these errors were encountered: