GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — codehike/.github/scripts at next · code-hike/codehike

Expand file tree

/

scripts

/
Copy path

Directory actions

More options

More options

Directory actions

More options

More options

Latest commit

 

History

History
History
/

scripts

/
Copy path

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
git-utils.mjs
git-utils.mjs
 
 
md-utils.mjs
md-utils.mjs
 
 
params.mjs
params.mjs
 
 
pr-merged.mjs
pr-merged.mjs
 
 
pr-updated.mjs
pr-updated.mjs
 
 
prepare-release.mjs
prepare-release.mjs
 
 
readme.md
readme.md
 
 
release.mjs
release.mjs
 
 
website-pr.mjs
website-pr.mjs
 
 

readme.md

Outline

First:

  • fill the right values in .github/scripts/params.mjs
  • add canary.json to gitignore
  • add NPM_TOKEN to secrets
  • enable PR creation for Actions
    • go to https://github.com/organizations/YOUR_ORG/settings/actions and check Allow GitHub Actions to create and approve pull requests
    • then go to https://github.com/YOUR_ORG/YOUR_REPO/settings/actions and check the box that previously was grayed out

pr-updated

For every new commit in a PR to next:

- build package
- if no new changeset
  - (update) comment with a link to add a changeset in the PR
- if new changeset
  - add `changeset` label to the PR
  - (update) comment with the canary install in the PR

pr-merged

For every merged PR to next that contains the changeset label:

- find the issues closed by the PR
- for every issue
  - add a comment with the canary install

push-to-next

For every push to next:

- build package
- if no changes, skip
- checkout and reset the `release` branch
- run `pnpm version-packages`
- push the `release` branch
- create or update release PR
  - body: changelog
  - labels: `release`
- create a PR from 'next' to 'main' if it doesn't exist
  - title: Update website

release-pr-merged

for every release pr merged to next:

- run build and  `pnpm release`
- push tags
- create github release
- find all `changeset` PRs
  - find related issues
    - add comments in fixed issues
  - remove `changeset` label

sponsors

You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.