Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

fix: update contributing.md #8470

Merged
merged 3 commits into from Oct 10, 2022
Merged

fix: update contributing.md #8470

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
efc42b5
Revert "fix(#6708): change domain order for union with (#8451)"
kanitw Oct 10, 2022
8d875e7
fix: Revert "Revert "fix(#6708): change domain order for union with (…
kanitw Oct 10, 2022
f02f3d3
fix: update contributing.md
kanitw Oct 10, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
2 changes: 1 addition & 1 deletion CONTRIBUTING.md
View file
Open in desktop
Expand Up @@ -196,7 +196,7 @@ During development, it can be convenient to rebuild automatically or to run test

### Deployment

Publishing is handled by a 2-branch [pre-release process](https://intuit.github.io/auto/docs/generated/shipit#next-branch-default), configured in `publish.yml`. All changes should be based off the default `next` branch, and are published automatically.
Publishing is handled by a 2-branch [pre-release process](https://intuit.github.io/auto/docs/generated/shipit#next-branch-default), configured in `publish-to-npm.yml`. All changes should be based off the default `next` branch, and are published automatically.

- PRs made into the default branch are auto-deployed to the `next` pre-release tag on NPM. The result can be installed with `npm install vega-lite/@next`.
- When merging into `next`, please use the `squash and merge` strategy.
Expand Down