-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Project automation: Rewrite actions using JavaScript #17080
Conversation
21cbdad
to
d4ca647
Compare
@@ -64,6 +64,8 @@ | |||
"@wordpress/wordcount": "file:packages/wordcount" | |||
}, | |||
"devDependencies": { | |||
"@actions/core": "1.0.0", | |||
"@actions/github": "1.0.0", |
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.
Hmm, I wouldn't have thought these dependencies were needed in the root package.json.
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.
According to https://github.com/WordPress/gutenberg/blob/4665d7074dfeae43eac02b1d2e4ad5713832078e/packages/README.md#development-dependencies it's intended that way.
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 for the pointer @swissspidy.
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.
But these are also listed as dependencies
in packages/project-management-automation/package.json
. Surely they don't need to be declared twice? They seem more appropriate as dependencies
to me than as devDependencies
, since they're required for the runtime script of the module.
packages/pull-request-automation/src/add-first-time-contributor-label.js
Outdated
Show resolved
Hide resolved
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.
Love this, introduces a really nice scaffolding to add more automation to PRs, and ensures there won't be any extra noise if we do. ❤️
I'd be happy to see it merged and have smaller follow up PRs address the comments.
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.
Nice work here 🎉
c2ed9f9
to
3c22f92
Compare
@talldan @youknowriad: Pretty happy with this now! Have moved a few things around so will need another review.
|
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.
Double approving!
* Project automation: Rewrite actions using JavaScript * Project automation: Don't transpile or install all dependencies * Project automation: pull-request-automation -> project-management-automation * Project automation: Add explanatory comment for `npm install` hack * Project automation: Add debug statements * Project automation: Don't use GitHub's debug() function * Project automation: Use `payload` in tasks, not `context` * Project automation: Link to the relevant GitHub documentation
* Project automation: Rewrite actions using JavaScript * Project automation: Don't transpile or install all dependencies * Project automation: pull-request-automation -> project-management-automation * Project automation: Add explanatory comment for `npm install` hack * Project automation: Add debug statements * Project automation: Don't use GitHub's debug() function * Project automation: Use `payload` in tasks, not `context` * Project automation: Link to the relevant GitHub documentation
* Project automation: Rewrite actions using JavaScript * Project automation: Don't transpile or install all dependencies * Project automation: pull-request-automation -> project-management-automation * Project automation: Add explanatory comment for `npm install` hack * Project automation: Add debug statements * Project automation: Don't use GitHub's debug() function * Project automation: Use `payload` in tasks, not `context` * Project automation: Link to the relevant GitHub documentation
into rnmobile/add-autosave-to-mobile * 'rnmobile/master' of https://github.com/WordPress/gutenberg: (52 commits) [RNMobile] DarkMode improvements (#17309) Remove redundant bg color within button appender (#17325) Support group block on mobile (#17251) [RNMobile] Insure tapping at end of post inserts at end Recover border colors (#17269) [RNMobile] Fix dismiss keyboard button for the post title (#17260) Unify media placeholder and upload props within media-text (#17268) MediaUpload and MediaPlaceholder unify props (#17145) Add native support for the MediaText block (#16305) Activate Travis CI on rnmobile/master branch (#17229) [RNMobile] Native mobile release v1.11.0 (#17181) Apply box-sizing border-box properly to the notices components (#17066) Writing Flow: allow undo of patterns with BACKSPACE and ESC (#14776) Project automation: Rewrite actions using JavaScript (#17080) Build: remove global install of latest npm since we want to use the paired node/npm version (#17134) Writing Flow/Quote: allow splitting (#17121) Use `400` as a valid `font-weight` Add: Disabled block count in the block manager (#17103) Update video player style on mobile - Add a new gridicon play icon, from: https://github.com/Automattic/gridicons/blob/87c9fce08b4a9f184b9fb4963228757fdd4f4e74/svg-min/gridicons-play.svg - Replace the Dashicon play by this one - Update icon size and icon color - Update the overlay color [RNMobile] Hide replaceable block when adding block (#16931) ... # Conflicts: # packages/block-editor/src/components/block-list/index.native.js # packages/block-editor/src/components/inserter/index.native.js # packages/block-editor/src/components/inserter/menu.native.js # packages/block-editor/src/components/media-placeholder/index.native.js # packages/block-editor/src/components/warning/index.native.js # packages/block-library/src/code/edit.native.js # packages/block-library/src/image/edit.native.js # packages/block-library/src/missing/edit.native.js # packages/block-library/src/more/edit.native.js # packages/block-library/src/nextpage/edit.native.js # packages/block-library/src/video/edit.native.js # packages/components/src/mobile/bottom-sheet/cell.native.js # packages/components/src/mobile/bottom-sheet/index.native.js # packages/components/src/mobile/dark-mode/index.native.js # packages/components/src/mobile/html-text-input/index.native.js # packages/components/src/toolbar/toolbar-container.native.js # packages/edit-post/src/components/header/header-toolbar/index.native.js # packages/edit-post/src/components/layout/index.native.js # packages/edit-post/src/components/visual-editor/index.native.js # packages/rich-text/src/component/index.native.js
Replaces all of our Docker container actions with a single JavaScript action.
This has a few benefits:
Docs: https://help.github.com/en/categories/automating-your-workflow-with-github-actions