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

benchmark: Rename permission-fs-read.js to permission-processhas-fs-read.js #49770

Merged
merged 1 commit into from Oct 23, 2023

Conversation

aki0501
Copy link
Contributor

@aki0501 aki0501 commented Sep 22, 2023

…esshas-fs-read.js

GHC OSD '23

@nodejs-github-bot nodejs-github-bot added benchmark Issues and PRs related to the benchmark subsystem. permission Issues and PRs related to the Permission Model labels Sep 22, 2023
Copy link
Member

@RafaelGSS RafaelGSS left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @aki0501

Thank you for your contribution. Can you please adjust the commit message? It must contain the namespace first, in your case, benchmark.

Therefore, your commit message should be: benchmark: rename permission-fs-read.js to permission-processhas-fs-read.js

You can do it by running

git commit --amend -> adjust your message
git push -f origin main

@aki0501
Copy link
Contributor Author

aki0501 commented Sep 22, 2023

Thank you for letting me know! I just modified the commit message and pushed it, I hope that worked.

@RafaelGSS RafaelGSS changed the title Rename benchmarks/permission/permission-fs-read.js to permission-proc… benchmark: Rename permission-fs-read.js to permission-processhas-fs-read.js Sep 22, 2023
@RafaelGSS
Copy link
Member

Hi @aki0501 looks like you've crossed the limit of a commit length (72 characters). Can you reduce it somehow? Maybe rewording it to:

benchmark: move permission-fs-read to permission-processhas-fs-read

@tniessen tniessen added the code-and-learn Issues related to the Code-and-Learn events and PRs submitted during the events. label Sep 22, 2023
@aki0501
Copy link
Contributor Author

aki0501 commented Sep 22, 2023

Just fixed it, sorry about that! Thank you again.

Copy link
Member

@RafaelGSS RafaelGSS left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.

@RafaelGSS RafaelGSS added the author ready PRs that have at least one approval, no pending requests for changes, and a CI started. label Sep 24, 2023
@aduh95 aduh95 closed this Oct 6, 2023
@aduh95 aduh95 reopened this Oct 6, 2023
@RafaelGSS RafaelGSS added the commit-queue Add this label to land a pull request using GitHub Actions. label Oct 7, 2023
@nodejs-github-bot nodejs-github-bot removed the commit-queue Add this label to land a pull request using GitHub Actions. label Oct 7, 2023
@nodejs-github-bot
Copy link
Collaborator

Commit Queue failed
- Loading data for nodejs/node/pull/49770
✔  Done loading data for nodejs/node/pull/49770
----------------------------------- PR info ------------------------------------
Title      benchmark: Rename permission-fs-read.js to permission-processhas-fs-read.js (#49770)
   ⚠  Could not retrieve the email or name of the PR author's from user's GitHub profile!
Branch     aki0501:main -> nodejs:main
Labels     benchmark, code-and-learn, author ready, permission
Commits    1
 - benchmark: move permission-fs-read to permission-processhas-fs-read
Committers 1
 - Aki Hasegawa-Johnson <104283523+aki0501@users.noreply.github.com>
PR-URL: https://github.com/nodejs/node/pull/49770
Reviewed-By: Rafael Gonzaga 
------------------------------ Generated metadata ------------------------------
PR-URL: https://github.com/nodejs/node/pull/49770
Reviewed-By: Rafael Gonzaga 
--------------------------------------------------------------------------------
   ℹ  This PR was created on Fri, 22 Sep 2023 18:43:41 GMT
   ✔  Approvals: 1
   ✔  - Rafael Gonzaga (@RafaelGSS) (TSC): https://github.com/nodejs/node/pull/49770#pullrequestreview-1641080960
   ℹ  This PR is being fast-tracked because it is from a Code and Learn event
   ✘  Last GitHub CI failed
   ℹ  Green GitHub CI is sufficient
--------------------------------------------------------------------------------
   ✔  Aborted `git node land` session in /home/runner/work/node/node/.ncu
https://github.com/nodejs/node/actions/runs/6438758931

@nodejs-github-bot nodejs-github-bot added the commit-queue-failed An error occurred while landing this pull request using GitHub Actions. label Oct 7, 2023
@RafaelGSS RafaelGSS removed the commit-queue-failed An error occurred while landing this pull request using GitHub Actions. label Oct 7, 2023
@aduh95 aduh95 merged commit 91a21a2 into nodejs:main Oct 23, 2023
39 of 45 checks passed
@aduh95
Copy link
Contributor

aduh95 commented Oct 23, 2023

Landed in 91a21a2, thanks for the contribution

alexfernandez pushed a commit to alexfernandez/node that referenced this pull request Nov 1, 2023
PR-URL: nodejs#49770
Reviewed-By: Rafael Gonzaga <rafael.nunu@hotmail.com>
targos pushed a commit that referenced this pull request Nov 11, 2023
PR-URL: #49770
Reviewed-By: Rafael Gonzaga <rafael.nunu@hotmail.com>
UlisesGascon pushed a commit that referenced this pull request Dec 11, 2023
PR-URL: #49770
Reviewed-By: Rafael Gonzaga <rafael.nunu@hotmail.com>
@UlisesGascon UlisesGascon mentioned this pull request Dec 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
author ready PRs that have at least one approval, no pending requests for changes, and a CI started. benchmark Issues and PRs related to the benchmark subsystem. code-and-learn Issues related to the Code-and-Learn events and PRs submitted during the events. permission Issues and PRs related to the Permission Model
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants