Skip to content

docs: rename the "aio" component to "docs-infra" - #24295

Closed
vicb wants to merge 1 commit into
angular:masterfrom
vicb:0604-docsInfra
Closed

vicb wants to merge 1 commit into
angular:masterfrom
vicb:0604-docsInfra

Conversation

@vicb

@vicb vicb commented Jun 4, 2018 •

Copy link
Copy Markdown
Contributor

The legacy "aio" is still active for currently pending PRs,
The GH label has been renamed as well

The legacy "aio" is still active for currently pending PRs,
The GH label has been renamed as well
@vicb vicb added action: review The PR is still awaiting reviews from at least one requested reviewer comp: docs-infra target: patch This PR is targeted for the next patch release labels Jun 4, 2018
@vicb vicb added action: merge The PR is ready for merge by the caretaker and removed action: review The PR is still awaiting reviews from at least one requested reviewer labels Jun 5, 2018
vicb added a commit that referenced this pull request Jun 5, 2018
The legacy "aio" is still active for currently pending PRs,
The GH label has been renamed as well

PR Close #24295
@vicb vicb closed this in 83a0686 Jun 5, 2018
gkalpak added a commit to gkalpak/angular that referenced this pull request Jun 11, 2018
mhevery pushed a commit that referenced this pull request Jun 12, 2018
mhevery pushed a commit that referenced this pull request Jun 12, 2018
@vicb
vicb deleted the 0604-docsInfra branch August 3, 2018 19:08
gkalpak added a commit to gkalpak/angular that referenced this pull request Aug 27, 2019
The `aio` commit message scope was renamed to `docs-infra` (which is
more descriptive) in angular#24295. Although it has been removed from the
documentation, the legacy `aio` scope was kept in the [list of valid
scopes][1] to cater for in-flight PRs that already used it. As a result,
it still shows up as a recommended, valid scope in the error message
shown when commit message validation fails during `git commit`. This is
misleading, especially for new contributors.

Since we have been "manually" discouraging people from using `aio`,
there should be no open PRs by now (and if there are, they should be
changed to `docs-infra`), so it is safe to remove it from the list of
allowed scopes.

Related discussion:
angular#32273 (review)

[1]: https://github.com/angular/angular/blob/3df54be9e/tools/validate-commit-message/commit-message.json#L16
atscott pushed a commit that referenced this pull request Aug 27, 2019
The `aio` commit message scope was renamed to `docs-infra` (which is
more descriptive) in #24295. Although it has been removed from the
documentation, the legacy `aio` scope was kept in the [list of valid
scopes][1] to cater for in-flight PRs that already used it. As a result,
it still shows up as a recommended, valid scope in the error message
shown when commit message validation fails during `git commit`. This is
misleading, especially for new contributors.

Since we have been "manually" discouraging people from using `aio`,
there should be no open PRs by now (and if there are, they should be
changed to `docs-infra`), so it is safe to remove it from the list of
allowed scopes.

Related discussion:
#32273 (review)

[1]: https://github.com/angular/angular/blob/3df54be9e/tools/validate-commit-message/commit-message.json#L16

PR Close #32341
atscott pushed a commit that referenced this pull request Aug 27, 2019
The `aio` commit message scope was renamed to `docs-infra` (which is
more descriptive) in #24295. Although it has been removed from the
documentation, the legacy `aio` scope was kept in the [list of valid
scopes][1] to cater for in-flight PRs that already used it. As a result,
it still shows up as a recommended, valid scope in the error message
shown when commit message validation fails during `git commit`. This is
misleading, especially for new contributors.

Since we have been "manually" discouraging people from using `aio`,
there should be no open PRs by now (and if there are, they should be
changed to `docs-infra`), so it is safe to remove it from the list of
allowed scopes.

Related discussion:
#32273 (review)

[1]: https://github.com/angular/angular/blob/3df54be9e/tools/validate-commit-message/commit-message.json#L16

PR Close #32341
sabeersulaiman pushed a commit to sabeersulaiman/angular that referenced this pull request Sep 6, 2019
The `aio` commit message scope was renamed to `docs-infra` (which is
more descriptive) in angular#24295. Although it has been removed from the
documentation, the legacy `aio` scope was kept in the [list of valid
scopes][1] to cater for in-flight PRs that already used it. As a result,
it still shows up as a recommended, valid scope in the error message
shown when commit message validation fails during `git commit`. This is
misleading, especially for new contributors.

Since we have been "manually" discouraging people from using `aio`,
there should be no open PRs by now (and if there are, they should be
changed to `docs-infra`), so it is safe to remove it from the list of
allowed scopes.

Related discussion:
angular#32273 (review)

[1]: https://github.com/angular/angular/blob/3df54be9e/tools/validate-commit-message/commit-message.json#L16

PR Close angular#32341
@angular-automatic-lock-bot

Copy link
Copy Markdown

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot Bot locked and limited conversation to collaborators Sep 13, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

action: merge The PR is ready for merge by the caretaker cla: yes target: patch This PR is targeted for the next patch release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants