-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Create wip #2443
Create wip #2443
Conversation
Adding WIP to new PRs
✅ Deploy Preview for actualbudget ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Bundle Stats — desktop-clientHey there, this message comes from a GitHub action that helps you and reviewers to understand how these changes affect the size of this project's bundle. As this PR is updated, I'll keep you updated on how the bundle size is impacted. Total
Changeset No files were changed View detailed bundle breakdownAdded No assets were added Removed No assets were removed Bigger No assets were bigger Smaller No assets were smaller Unchanged
|
Bundle Stats — loot-coreHey there, this message comes from a GitHub action that helps you and reviewers to understand how these changes affect the size of this project's bundle. As this PR is updated, I'll keep you updated on how the bundle size is impacted. Total
Changeset No files were changed View detailed bundle breakdownAdded No assets were added Removed No assets were removed Bigger No assets were bigger Smaller No assets were smaller Unchanged
|
notes
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will this work for PRs coming from forks?
Co-authored-by: Matiss Janis Aboltins <[email protected]>
Co-authored-by: Matiss Janis Aboltins <[email protected]>
Co-authored-by: Matiss Janis Aboltins <[email protected]>
I'm not sure. Can we test it somehow? |
Create a new repository with the action. Fork it. And then submit a PR to it. |
I can't get it working. I'm a bit outside my depth here. |
@carkom the workflow is missing a run line and getting this error:
https://github.com/actualbudget/actual/actions/runs/8217141693 |
Yes, indeed. Do you know how to fix it? I'm a bit out of my depth on this one. |
Simply passing the new new title to Here is a version that works, but still needs some work (not add WIP if already found in the title for example, and maybe we should have some other escape to prevent it from running when we know we don't want it to WIP)
|
Thanks @twk3. Super helpful. The idea was to add WIP always. What scenarios do you forsee where we'd want to skip this rule? |
Here, I think this will work:
This will skip if WIP is already in the title (so we don't add it again). Skip if opened in draft (taffico will already add WIP label). Skip if already labeled as WIP by the PR creator. (doesn't really matter, but saves them from having to edit the title later), and skips if a reviewer is assigned right from review creation (I think this makes sense, AND gives us an escape if a maintainer is trying to get in a quick release related fix during the release procedures for example) |
@MatissJanis , I've tested this on a dummy fork. Working as expected. Thanks @twk3 !! |
I don't think this would work in Would you mind sending the link where you tested it? |
Master repo is on my profile. Forked that master from actualbudget project. Sent PR via acutal (forked repo). The job picked it up and changed the title. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
Sorry, slight change to syntax change "WIP: " to "[WIP] " |
Adding WIP to new PRs