pronamic / wp-deployer Goto Github PK

4.0 4.0 0.0 227 KB

✗ [DEPRECATED] Console application to build and deploy WordPress solutions to the WordPress.org repository and AWS S3. Pronamic CLI is the successor of this project: https://github.com/pronamic/pronamic-cli.

PHP 98.22% CSS 1.78%

aws-s3 build deploy deployment deprecated wordpress

wp-deployer's People

Contributors

Stargazers

Watchers

wp-deployer's Issues

Add `bin/wp-build` for juist building the WordPress solution?

Renamed and removed tags are pushed

Colleagues who still have old tags locally will push them automatically?

https://github.com/pronamic/wp-deployer/blob/778fa74c200fd5d9d6d34dabd2b83af593ddbd29/src/VersionCommand.php#LL566C35-L566C50

See for example:
https://github.com/pronamic/wp-pronamic-pay-gravityforms/tags

CC @rvdsteege

GitHub release assets added from `build/*.zip` inconvenient

wp-deployer/src/VersionCommand.php

Lines 581 to 598 in 10ed16a

    
           		/** 
        
           		 * GitHub release. 
        
           		 *  
        
           		 * @link https://cli.github.com/manual/gh_release_create 
        
           		 */ 
        
           		$io->title( 'GitHub release' ); 
        
           		$assets = \array_map( 
        
           			'\escapeshellarg', 
        
           			\glob( $cwd . '/build/*.zip' ) 
        
           		); 
        
           		$command = \sprintf( 
        
           			'gh release create %s --title %s --notes-file - %s', 
        
           			$tagname, 
        
           			\escapeshellarg( $new_version ), 
        
           			\implode( ' ', $assets ) 
        
           		);

Added in 177c421 by @rvdsteege. We don't know if users have a build folder and the *.zip are up to date. In the release of a plugin an old ZIP file was attached to the release since i didn't have a build script in place.

https://github.com/pronamic/wp-pronamic-pay/blob/ddb3cc968144f9619d5d6121e4c90b821967f8d2/composer.json#L121-L123

After release merge `develop` in `main`?

No empty line `Full set of changes`

### Composer

- Changed `php` from `>=8.0` to `>=7.4`.
Full set of changes: [`4.7.0...4.7.1`][4.7.1]

Bulk prefix version tags with `v`, for example: `1.0.0` → `v1.0.0`

GitHub advices to use the v prefix on the new release page: https://github.com/pronamic/wp-deployer/releases/new.

Tagging suggestions

It’s common practice to prefix your version names with the letter v. Some good tag names might be v1.0.0 or v2.3.4.

The wp-deployer version command will do this by default, but @pronamic we didn't do this by default. This results in a mix of 1.0.0 and v.1.0.1 tagnames, which is inconvenient when executing certain commands:

wp-deployer/src/VersionCommand.php

Lines 878 to 880 in 845a6db

    
           $tagname = 'v' . $version; 
        
           $object = 'tags/' . $tagname . ':composer.lock';

Should or can we prefix all tags with a v?
https://gist.github.com/knu/111055

Rename to `pronamic-cli` and merge `pronamic/wp-backup`?

https://github.com/pronamic/wp-backup

Display bump version result

wp-deployer/src/VersionCommand.php

Lines 237 to 252 in 778fa74

    
           		/** 
        
           		 * New version. 
        
           		 *  
        
           		 * @link https://docs.npmjs.com/cli/v8/commands/npm-version#description 
        
           		 * @link https://github.com/npm/node-semver#functions 
        
           		 */ 
        
           		$bump_method = $io->choice( 
        
           			'Select bump method', 
        
           			[ 
        
           				'major', 
        
           				'minor', 
        
           				'patch', 
        
           			], 
        
           			'patch'  
        
           		);

The choice function does not allow for labels as far as i know:
https://symfony.com/doc/current/console/style.html#user-input-methods

It would be great if we can display what version the patch, minor and major options will result in.

Display GitHub release URL after creating

https://github.com/pronamic/wp-number/releases/tag/v1.2.1

Run `composer run-script version` if available

Check composer.json scripts property for version script and run if defined.

preversion
version
postversion

Run the preversion script. These scripts have access to the old version in package.json. A typical use would be running your full test suite before deploying. Any files you want added to the commit should be explicitly added using git add.

Run the version script. These scripts have access to the new version in package.json (so they can incorporate it into file headers in generated files for example). Again, scripts should explicitly add generated files to the commit using git add.

Run the postversion script. Use it to clean up the file system or automatically push the commit and/or tag.

pronamic / wp-deployer Goto Github PK

wp-deployer's People

Contributors

Stargazers

Watchers

wp-deployer's Issues

Add `bin/wp-build` for juist building the WordPress solution?

Renamed and removed tags are pushed

GitHub release assets added from `build/*.zip` inconvenient

After release merge `develop` in `main`?

No empty line `Full set of changes`

Bulk prefix version tags with `v`, for example: `1.0.0` → `v1.0.0`

Tagging suggestions

Rename to `pronamic-cli` and merge `pronamic/wp-backup`?

Display bump version result

Display GitHub release URL after creating

Run `composer run-script version` if available

Recommend Projects

React

Vue.js

Typescript

TensorFlow

Django

Laravel

D3

Recommend Topics

javascript

web

server

Machine learning

Visualization

Game

Recommend Org

Facebook

Microsoft

Google

Alibaba

D3

Tencent

	/**
	* GitHub release.
	*
	* @link https://cli.github.com/manual/gh_release_create
	*/
	$io->title( 'GitHub release' );

	$assets = \array_map(
	'\escapeshellarg',
	\glob( $cwd . '/build/*.zip' )
	);

	$command = \sprintf(
	'gh release create %s --title %s --notes-file - %s',
	$tagname,
	\escapeshellarg( $new_version ),
	\implode( ' ', $assets )
	);

	$tagname = 'v' . $version;

	$object = 'tags/' . $tagname . ':composer.lock';

	/**
	* New version.
	*
	* @link https://docs.npmjs.com/cli/v8/commands/npm-version#description
	* @link https://github.com/npm/node-semver#functions
	*/
	$bump_method = $io->choice(
	'Select bump method',
	[
	'major',
	'minor',
	'patch',
	],
	'patch'
	);