Skip to content

Commit

Permalink
maint: update repo for pipeline team ownership (#306)
Browse files Browse the repository at this point in the history
## Which problem is this PR solving?

- finish handoff of repo to pipeline team

## Short description of the changes

- add github workflow for github project
- remove now unused workflows
- fix dependabot groups
- add release.yml for release notes
- add more detail to releasing doc 
- we may want more changes later after we release, for now just doing
known details
  • Loading branch information
JamieDanielson authored May 28, 2024
1 parent 7960572 commit 592fede
Show file tree
Hide file tree
Showing 6 changed files with 65 additions and 65 deletions.
16 changes: 9 additions & 7 deletions .github/dependabot.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -5,14 +5,7 @@ updates:
directory: "/"
schedule:
interval: "monthly"
- package-ecosystem: "github-actions"
directory: "/"
schedule:
interval: "monthly"
groups:
"@actions":
patterns:
- "@actions/*"
dev-dependencies:
patterns:
- "@types/node"
Expand All @@ -22,3 +15,12 @@ updates:
- "js-yaml"
- "prettier"
- "typescript"

- package-ecosystem: "github-actions"
directory: "/"
schedule:
interval: "monthly"
groups:
"@actions":
patterns:
- "@actions/*"
25 changes: 25 additions & 0 deletions .github/release.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,25 @@
# .github/release.yml

changelog:
exclude:
labels:
- no-changelog
categories:
- title: 💥 Breaking Changes 💥
labels:
- "version: bump major"
- breaking-change
- title: 💡 Enhancements
labels:
- "type: enhancement"
- title: 🐛 Fixes
labels:
- "type: bug"
- title: 🛠 Maintenance
labels:
- "type: maintenance"
- "type: dependencies"
- "type: documentation"
- title: 🤷 Other Changes
labels:
- "*"
15 changes: 15 additions & 0 deletions .github/workflows/add-to-project-v2.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,15 @@
name: Add to project
on:
issues:
types: [opened]
pull_request_target:
types: [opened]
jobs:
add-to-project:
runs-on: ubuntu-latest
name: Add issues and PRs to project
steps:
- uses: actions/add-to-project@main
with:
project-url: https://github.com/orgs/honeycombio/projects/27
github-token: ${{ secrets.GHPROJECTS_TOKEN }}
22 changes: 0 additions & 22 deletions .github/workflows/gh-issue-to-asana.yml

This file was deleted.

28 changes: 0 additions & 28 deletions .github/workflows/gh-pr-to-asana.yml

This file was deleted.

24 changes: 16 additions & 8 deletions RELEASING.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,20 +4,28 @@

Follow these steps to create a new release:

- Create a release-prep branch:
- Update version in package.json
- Update CHANGELOG for this version
- Commit, push branch, open PR, get a review of release prep changes, and merge
- Once the pull request is merged, fetch the updated main branch.
- Apply a tag for the new version on the merged commit on main: vX.Y.Z, for example v1.1.2: `git tag -a v1.1.2 -m "v1.1.2"`
- Push the new version tag: `git push origin v1.1.2`
- Use `npm version --no-git-tag-version` to update the version number using `major`, `minor`, `patch`, or the prerelease variants `premajor`, `preminor`, or `prepatch`.
For example, to bump from v1.1.1 to the next patch version:

```shell
> npm version --no-git-tag-version patch # 1.1.1 -> 1.1.2
```

- Confirm the version number update appears in package.json and package-lock.json.
- Update `CHANGELOG.md` with the changes since the last release. Consider automating with a command such as these two:
- `git log $(git describe --tags --abbrev=0)..HEAD --no-merges --oneline > new-in-this-release.log`
- `git log --pretty='%C(green)%d%Creset- %s | [%an](https://github.com/)'`
- Commit changes, push, and open a release preparation pull request for review.
- Once the pull request is merged, fetch the updated `main` branch.
- Apply a tag for the new version on the merged commit (e.g. `git tag -a v2.3.1 -m "v2.3.1"`)
- Push the tag upstream (this will kick off the release pipeline in CI) e.g. `git push origin v2.3.1`
- Create a new release from [the Releases page](https://github.com/honeycombio/gha-buildevents/releases)
- check the "Publish this release to the GitHub Marketplace" box
- choose the version tag created above
- release title matches version number
- copy and paste the changelog entry for this version into the release description
- Update the major version tag so it points to the latest release
- with the latest release checked out locally:
- with the latest release checked out locally:

```shell
git tag -fa v1 -m "Update v1 tag"
Expand Down

0 comments on commit 592fede

Please sign in to comment.