-
Notifications
You must be signed in to change notification settings - Fork 0
update expo fp version #3
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
This file was deleted.
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,13 @@ | ||
| name: tagpr | ||
| on: | ||
| push: | ||
| branches: ["main"] | ||
| jobs: | ||
| tagpr: | ||
| permissions: write-all | ||
| runs-on: ubuntu-latest | ||
| steps: | ||
| - uses: actions/checkout@v4 | ||
| - uses: Songmu/tagpr@v1 | ||
| env: | ||
| GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} | ||
|
Comment on lines
+11
to
+13
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 🛠️ Refactor suggestion Consider using a more specific version of tagpr and add a comment explaining its purpose. While using the tagpr action is good for automated versioning and tagging, and the GITHUB_TOKEN usage is secure, there are a couple of suggestions:
Here's a suggested improvement: - name: Run tagpr
uses: Songmu/tagpr@v1.1.1 # Pin to a specific version
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
# This action automates versioning and tagging based on conventional commitsAlso, ensure that your commit messages follow the conventional commits format for this action to work effectively. |
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🛠️ Refactor suggestion
Consider restricting permissions.
While the job name "tagpr" is consistent with the workflow name, the "write-all" permission is very broad. It's generally recommended to follow the principle of least privilege.
Consider restricting the permissions to only what's necessary for the tagpr action. For example:
This would allow the action to create tags, releases, and pull requests without granting unnecessary permissions.