Move repository to PHPCSStandards organisation #146
Comments
|
As this motion has been seconded by both other active maintainers, lets make the move! |
|
The one thing we should still discuss about this - should the package also be renamed to The downside of that is that 1) the stats won't be retained and 2) it will be quite a while before all users have switched over. |
|
My current thinking is (more or less) that we should rename to Regarding renaming, we might want to take it one step further and go from |
|
Also... Do we have any reason for not pressing the "transfer" button right now?
|
Fair enough, clean slate and all. For the record, current stats are pretty impressive already:
I agree, sounds like a good plan. On that note, we can rename the repo to
Go for it! I'll handle the accepting on the other end. |
Does GitHub auto-redirect on a change like that? |
@jrfnl Looks like I'm not allowed: |
@Potherca Huh ? That sounds weird - In my view, a transfer request should be allowed to be initiated by any admin of a repo with the acceptance being the responsibility of the organisation on the other end (with a mail notifying them there is a transfer request to accept). May be something weird on GH's end. I'll give it a try myself. Didn't want to do that before as for "auditability/transparency" it is, of course, better if the transfer is done by multiple people showing that there is consensus about it. As a side-note: I have already invited both you as well as @mjrider to the PHPCSStandards organisation, but looks like neither of you have accepted yet. |
Looks like that worked. Shall I rename the repo to `composer-installer straight away as well ? |
Yes please, the sooner the better IMHO. |
Done! |
|
I had this issue open before the change was made, and I can confirm that GitHub successfully redirected me back to this issue when reloading the page. 👍🏻 Suggest: close. |
|
@GaryJones Thanks for confirming. The issue will automatically be closed when #158 gets merged, which updates the references to the repo location in all relevant places in the code base. |
|
@mjrider Looks like I don't get a notification mail when an invite to an organisation is accepted. Could you please leave a note here when you have ? I will then add you to the "composer plugin admins" team, which should give you admin access to the repo again. |
Using the `dealerdirect/phpcodesniffer-composer-installer` Composer plugin is recommended to register external PHPCS standards with PHPCS. As of Composer 2.2.0, Composer plugins need to be explicitly allowed to run. This commit: * Adds the necessary configuration for that to the `composer.json` for this project. * Adds the CLI command to set those permissions to the installation instructions for consumer projects. Includes updating the URL references to the plugin to point to the new home of the plugin. (see [upstream issue sirbrillig#146](PHPCSStandards/composer-installer#146)) Refs: * https://blog.packagist.com/composer-2-2/#more-secure-plugin-execution
The Composer plugin has a new home. Ref: PHPCSStandards/composer-installer#146
The Composer plugin has a new home. Ref: PHPCSStandards/composer-installer#146
The Composer plugin has a new home. Ref: PHPCSStandards/composer-installer#146
The Composer plugin has a new home. Ref: PHPCSStandards/composer-installer#146
The `dealerdirect/phpcodesniffer-composer-installer` Composer plugin is a non-dev requirement for PHPCSUtils. As of Composer 2.2.0, Composer plugins need to be explicitly allowed to run. This commit updates the installation instructions to handle this. It also adds an info block suggesting how to handle this for external standards including PHPCSUtils. Includes updating the URL references to the plugin to point to the new home of the plugin. (see [upstream issue #146](PHPCSStandards/composer-installer#146)) Refs: * https://blog.packagist.com/composer-2-2/#more-secure-plugin-execution
The `dealerdirect/phpcodesniffer-composer-installer` Composer plugin is a non-dev requirement for PHPCSUtils. As of Composer 2.2.0, Composer plugins need to be explicitly allowed to run. This commit updates the installation instructions to handle this. It also adds an info block suggesting how to handle this for external standards including PHPCSUtils. Includes updating the URL references to the plugin to point to the new home of the plugin. (see [upstream issue #146](PHPCSStandards/composer-installer#146)) Refs: * https://blog.packagist.com/composer-2-2/#more-secure-plugin-execution
The Composer plugin has a new home. Ref: PHPCSStandards/composer-installer#146
Using the `dealerdirect/phpcodesniffer-composer-installer` Composer plugin is recommended to register external PHPCS standards with PHPCS. As of Composer 2.2.0, Composer plugins need to be explicitly allowed to run. This commit: * Adds the necessary configuration for that to the `composer.json` for this project. * Adds the CLI command to set those permissions to the installation instructions for consumer projects. Includes updating the URL references to the plugin to point to the new home of the plugin. (see [upstream issue #146](PHPCSStandards/composer-installer#146)) Refs: * https://blog.packagist.com/composer-2-2/#more-secure-plugin-execution Co-authored-by: jrfnl <jrfnl@users.noreply.github.com>
Using the `dealerdirect/phpcodesniffer-composer-installer` Composer plugin is recommended to register external PHPCS standards with PHPCS. As of Composer 2.2.0, Composer plugins need to be explicitly allowed to run. This commit: * Adds the necessary configuration for that to the `composer.json` for this project. * Adds the CLI command to set those permissions to the installation instructions for consumer projects. Includes updating the URL references to the plugin to point to the new home of the plugin. (see [upstream issue WordPress#146](PHPCSStandards/composer-installer#146)) Refs: * https://blog.packagist.com/composer-2-2/#more-secure-plugin-execution
Using the `dealerdirect/phpcodesniffer-composer-installer` Composer plugin is recommended to register external PHPCS standards with PHPCS. As of Composer 2.2.0, Composer plugins need to be explicitly allowed to run. This commit: * Adds the necessary configuration for that to the `composer.json` for this project. * Adds the CLI command to set those permissions to the installation instructions for consumer projects. Includes updating the URL references to the plugin to point to the new home of the plugin. (see [upstream issue WordPress#146](PHPCSStandards/composer-installer#146)) Refs: * https://blog.packagist.com/composer-2-2/#more-secure-plugin-execution
Using the `dealerdirect/phpcodesniffer-composer-installer` Composer plugin is recommended to register external PHPCS standards with PHPCS. As of Composer 2.2.0, Composer plugins need to be explicitly allowed to run. This commit: * Adds the necessary configuration for that to the `composer.json` for this project. * Adds the CLI command to set those permissions to the installation instructions for consumer projects. Includes updating the URL references to the plugin to point to the new home of the plugin. (see [upstream issue WordPress#146](PHPCSStandards/composer-installer#146)) Refs: * https://blog.packagist.com/composer-2-2/#more-secure-plugin-execution
Using the `dealerdirect/phpcodesniffer-composer-installer` Composer plugin is recommended to register external PHPCS standards with PHPCS. As of Composer 2.2.0, Composer plugins need to be explicitly allowed to run. This commit: * Adds the necessary configuration for that to the `composer.json` for this project. * Adds the CLI command to set those permissions to the installation instructions for consumer projects. Includes updating the URL references to the plugin to point to the new home of the plugin. (see [upstream issue WordPress#146](PHPCSStandards/composer-installer#146)) Refs: * https://blog.packagist.com/composer-2-2/#more-secure-plugin-execution
Using the `dealerdirect/phpcodesniffer-composer-installer` Composer plugin is recommended to register external PHPCS standards with PHPCS. As of Composer 2.2.0, Composer plugins need to be explicitly allowed to run. This commit: * Adds the necessary configuration for that to the `composer.json` for this project. * Adds the CLI command to set those permissions to the installation instructions for consumer projects. Includes updating the URL references to the plugin to point to the new home of the plugin. (see [upstream issue WordPress#146](PHPCSStandards/composer-installer#146)) Refs: * https://blog.packagist.com/composer-2-2/#more-secure-plugin-execution
Using the `dealerdirect/phpcodesniffer-composer-installer` Composer plugin is recommended to register external PHPCS standards with PHPCS. As of Composer 2.2.0, Composer plugins need to be explicitly allowed to run. This commit: * Adds the necessary configuration for that to the `composer.json` for this project. * Adds the CLI command to set those permissions to the installation instructions for consumer projects. Includes updating the URL references to the plugin to point to the new home of the plugin. (see [upstream issue WordPress#146](PHPCSStandards/composer-installer#146)) Refs: * https://blog.packagist.com/composer-2-2/#more-secure-plugin-execution
Using the `dealerdirect/phpcodesniffer-composer-installer` Composer plugin is recommended to register external PHPCS standards with PHPCS. As of Composer 2.2.0, Composer plugins need to be explicitly allowed to run. This commit: * Adds the necessary configuration for that to the `composer.json` for this project. * Adds the CLI command to set those permissions to the installation instructions for consumer projects. Includes updating the URL references to the plugin to point to the new home of the plugin. (see [upstream issue WordPress#146](PHPCSStandards/composer-installer#146)) Refs: * https://blog.packagist.com/composer-2-2/#more-secure-plugin-execution
Using the `dealerdirect/phpcodesniffer-composer-installer` Composer plugin is recommended to register external PHPCS standards with PHPCS. As of Composer 2.2.0, Composer plugins need to be explicitly allowed to run. This commit: * Adds the necessary configuration for that to the `composer.json` for this project. * Adds the CLI command to set those permissions to the installation instructions for consumer projects. Includes updating the URL references to the plugin to point to the new home of the plugin. (see [upstream issue WordPress#146](PHPCSStandards/composer-installer#146)) Refs: * https://blog.packagist.com/composer-2-2/#more-secure-plugin-execution
Using the `dealerdirect/phpcodesniffer-composer-installer` Composer plugin is recommended to register external PHPCS standards with PHPCS. As of Composer 2.2.0, Composer plugins need to be explicitly allowed to run. This commit: * Adds the necessary configuration for that to the `composer.json` for this project. * Adds the CLI command to set those permissions to the installation instructions for consumer projects. Includes updating the URL references to the plugin to point to the new home of the plugin. (see [upstream issue WordPress#146](PHPCSStandards/composer-installer#146)) Refs: * https://blog.packagist.com/composer-2-2/#more-secure-plugin-execution
Using the `dealerdirect/phpcodesniffer-composer-installer` Composer plugin is recommended to register external PHPCS standards with PHPCS. As of Composer 2.2.0, Composer plugins need to be explicitly allowed to run. This commit: * Adds the necessary configuration for that to the `composer.json` for this project. * Adds the CLI command to set those permissions to the installation instructions for consumer projects. Includes updating the URL references to the plugin to point to the new home of the plugin. (see [upstream issue WordPress#146](PHPCSStandards/composer-installer#146)) Refs: * https://blog.packagist.com/composer-2-2/#more-secure-plugin-execution
Using the `dealerdirect/phpcodesniffer-composer-installer` Composer plugin is recommended to register external PHPCS standards with PHPCS. As of Composer 2.2.0, Composer plugins need to be explicitly allowed to run. This commit: * Adds the necessary configuration for that to the `composer.json` for this project. * Adds the CLI command to set those permissions to the installation instructions for consumer projects. Includes updating the URL references to the plugin to point to the new home of the plugin. (see [upstream issue WordPress#146](PHPCSStandards/composer-installer#146)) Refs: * https://blog.packagist.com/composer-2-2/#more-secure-plugin-execution
The Composer plugin has a new home. Ref: PHPCSStandards/composer-installer#146
The Composer plugin has a new home. Ref: PHPCSStandards/composer-installer#146
As mentioned before in #113 it is desirable to move this project to an organization that has more contributors and higher visibility.
Currently PHPCSStandards looks like the best match.
This issue proposes to move the repository for this project from the Dealerdirect organisation to PHPCSStandards.
Opinions?
The text was updated successfully, but these errors were encountered: