-
Notifications
You must be signed in to change notification settings - Fork 223
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.
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
skip ci prevents followup publish workflow run after merging release PR #198
Comments
@Andarist Could it be as simple as that that we need to update documentation to inform users to disable the |
confirmed. you either need to configure |
Hey @airtonix I don't know if you have figured out your problem but I can confirm some of these:
With those said, however, the act of merging a PR will trigger an Another important thing that took me a while to realize is that Here is my workflow: name: changesets
on:
push:
branches:
- main
workflow_dispatch:
jobs:
Version:
timeout-minutes: 15
runs-on: ubuntu-latest
steps:
- name: Checkout repository
uses: actions/checkout@v3
with:
fetch-depth: 0
- name: Setup pnpm
uses: pnpm/action-setup@v2
with:
version: 7.6.0
- name: Setup node
uses: actions/setup-node@v3
with:
node-version: 16
cache: pnpm
- name: Install dependencies
run: pnpm install --frozen-lockfile
- name: Create release PR or Publish to npm
uses: changesets/action@v1
with:
version: pnpm ci:version # changeset version
publish: pnpm ci:publish # pnpm build && changeset publish
commit: "chore(release): changesets versioning & publication"
title: "Changesets: Versioning & Publication"
createGithubReleases: true
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
NPM_TOKEN: ${{ secrets.NPM_TOKEN }} Push to I am working with a turborepo - pnpm monorepo setup, having migrated from semantic-release. You can have a look at my repo here. Everything works pretty nicely currently, including the automatically published github releases even though some people have filed issues with it. Also I know you are suffering over there but I couldn't help but have a laugh reading your issue description. |
@vnphanquang thanks for the clarification I was looking for. So, If i understand correctly: Correct me if I'm wrong please. |
@wijionejs yes pretty much. We can look at the actual source code of the action at https://github.com/changesets/action/blob/main/src/index.ts#L49-L116 (the switch cases pretty much tell us what's up) For me, i know that i only do publishing by merging a PR with changesets, so i added a path filter for my changsets action just to save some resources. Also I added a name: changesets
on:
push:
branches:
- main
+ paths:
+ - ".changeset/**"
+ - ".github/workflows/changesets.yaml"
+ workflow_dispatch: My action is at https://github.com/vnphanquang/svelte-put/blob/main/.github/workflows/changesets.yaml#L7-L8 if helpful |
@vnphanquang, great, thanks for the link to source code of the actions, it becomes even easier to understand how it works under the hood! |
Greetings, you have reached the true utopia of promises!
<angel voices>
except reality is
So lets recap the expected outcome of using this action...
push
event that runschangeset/action
on your default branch.push
event workflow should runchangeset/action
should create "Release PR" (because it finds.changeset/!(README)*.md
)push
event on your default branch (same workflow)If you just follow all the documentation you might just be cunning enough to get the "Release PR" to show up.
If you use the default
${{ secrets.GITHUB_TOKEN }}
for everything, then that's as far as you get... no more Crème Brûlée for you! ✋🏻 👮🏻So now you dive into the issue tickets with your search fu and sword of perseverance...
You find that:
So lets say you get there, you work out what scopes you need in your Personal Access Token...
${{secrets.GITHUB_TOKEN}}
used throughout this job. If you've changed the action settings in your REPO to just make it allwrite
then this might not be needed.actions/setup-node@v2
to configure your registryBut you're not out of the woods yet!...
Rolling like this, your "Version Packages" PR when merged will have in its commit message the hilariously troll like marker:
As a result, you still don't get a follow up workflow run.
So i have slain all the monsters in the dungeon only to discover that the all the loot is glitched and i cant pick it up or perhaps i am in the wrong dungeon?
how do we get make the follow up action run when we merge our "Version Packages" pr ?
default github bot git user:
The text was updated successfully, but these errors were encountered: