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.

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

Fix curling #3

Open
wants to merge 12 commits into
base: master
Choose a base branch
from
Open

Fix curling #3

wants to merge 12 commits into from

Conversation

rmccue
Copy link
Contributor

@rmccue rmccue commented May 13, 2016

Just a test to get the build. Fingers crossed this helps.

markjaquith referenced this pull request in markjaquith/WordPress Jun 1, 2016
This update adds two main features for your WordPress development happiness.

1) GitHub URL support. You can now use `grunt patch:https://github.com/aaronjorbin/develop.wordpress/pull/3` with any copy of WordPress on GitHub. No longer will you need to download the patch manually.  Works for both core and develop mirrors on GitHub.  

2) Upload patches directly from the command line. No longer will you need to create a patch and manually upload it to trac. `grunt upload_patch:20000` will upload a patch to the appropriate ticket after a user enters a WordPress.org username and password. This is limited to users with the appropriate XML-RPC privileges in trac (right now, that is just bug gardeners). You still need to manually add the `has patch` keyword.  

Full changelog: WordPress/grunt-patch-wordpress@0.3.0...0.4.0

Fixes #35917.
Props netweb, ericlewis, michaelbeil, jorbin.

Built from https://develop.svn.wordpress.org/trunk@37612


git-svn-id: http://core.svn.wordpress.org/trunk@37580 1a063a9b-81f0-0310-95a4-ce76da25c4cd
svn2github referenced this pull request in svn2github/wp-svn-2-git Jun 1, 2016
This update adds two main features for your WordPress development happiness.

1) GitHub URL support. You can now use `grunt patch:https://github.com/aaronjorbin/develop.wordpress/pull/3` with any copy of WordPress on GitHub. No longer will you need to download the patch manually.  Works for both core and develop mirrors on GitHub.  

2) Upload patches directly from the command line. No longer will you need to create a patch and manually upload it to trac. `grunt upload_patch:20000` will upload a patch to the appropriate ticket after a user enters a WordPress.org username and password. This is limited to users with the appropriate XML-RPC privileges in trac (right now, that is just bug gardeners). You still need to manually add the `has patch` keyword.  

Full changelog: WordPress/grunt-patch-wordpress@0.3.0...0.4.0

Fixes #35917.
Props netweb, ericlewis, michaelbeil, jorbin.

Built from https://develop.svn.wordpress.org/trunk@37612


git-svn-id: http://core.svn.wordpress.org/trunk@37580 1a063a9b-81f0-0310-95a4-ce76da25c4cd
janblaha referenced this pull request in janblaha/wordpress Jul 7, 2016
This update adds two main features for your WordPress development happiness.

1) GitHub URL support. You can now use `grunt patch:https://github.com/aaronjorbin/develop.wordpress/pull/3` with any copy of WordPress on GitHub. No longer will you need to download the patch manually.  Works for both core and develop mirrors on GitHub.  

2) Upload patches directly from the command line. No longer will you need to create a patch and manually upload it to trac. `grunt upload_patch:20000` will upload a patch to the appropriate ticket after a user enters a WordPress.org username and password. This is limited to users with the appropriate XML-RPC privileges in trac (right now, that is just bug gardeners). You still need to manually add the `has patch` keyword.  

Full changelog: WordPress/grunt-patch-wordpress@0.3.0...0.4.0

Fixes #35917.
Props netweb, ericlewis, michaelbeil, jorbin.

Built from https://develop.svn.wordpress.org/trunk@37612
staylor referenced this pull request in staylor/develop.svn.wordpress.org Aug 18, 2016
This update adds two main features for your WordPress development happiness.

1) GitHub URL support. You can now use `grunt patch:https://github.com/aaronjorbin/develop.wordpress/pull/3` with any copy of WordPress on GitHub. No longer will you need to download the patch manually.  Works for both core and develop mirrors on GitHub.  

2) Upload patches directly from the command line. No longer will you need to create a patch and manually upload it to trac. `grunt upload_patch:20000` will upload a patch to the appropriate ticket after a user enters a WordPress.org username and password. This is limited to users with the appropriate XML-RPC privileges in trac (right now, that is just bug gardeners). You still need to manually add the `has patch` keyword.  

Full changelog: WordPress/grunt-patch-wordpress@0.3.0...0.4.0

Fixes #35917.
Props netweb, ericlewis, michaelbeil, jorbin.


git-svn-id: https://develop.svn.wordpress.org@37612 602fd350-edb4-49c9-b593-d223f7449a82
nylen referenced this pull request in nylen/wordpress-develop-svn Feb 16, 2017
This update adds two main features for your WordPress development happiness.

1) GitHub URL support. You can now use `grunt patch:https://github.com/aaronjorbin/develop.wordpress/pull/3` with any copy of WordPress on GitHub. No longer will you need to download the patch manually.  Works for both core and develop mirrors on GitHub.  

2) Upload patches directly from the command line. No longer will you need to create a patch and manually upload it to trac. `grunt upload_patch:20000` will upload a patch to the appropriate ticket after a user enters a WordPress.org username and password. This is limited to users with the appropriate XML-RPC privileges in trac (right now, that is just bug gardeners). You still need to manually add the `has patch` keyword.  

Full changelog: WordPress/grunt-patch-wordpress@0.3.0...0.4.0

Fixes #35917.
Props netweb, ericlewis, michaelbeil, jorbin.


git-svn-id: https://develop.svn.wordpress.org/trunk@37612 602fd350-edb4-49c9-b593-d223f7449a82
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant