Comments (6)
Edit:
Solution
So I did just look around the settings within the actions settings and found the setting that did the trick for me
- Go to your repository's
Settings
tab. - Now on the left side nav bar under the category
Code and automation
click on theActions
dropdown button and select the optionGeneral
- Now scroll down in your page to the
Workflow permissions
here you should find 2 radio buttons, and a checkbox in the bottom, if you haven't made any changes here before your default radio button setting should be the second, namelyRead repository contents and packages permissions
, this setting prevents your action workflows from applying any changes to your repository's files. To change that simply select the radio button option above, namelyRead and write permissions
. Don't forget to click theSave
button in the end, which can be found in the bottom of theWorkflow permissions
section.
I hope this helps you gents @ZhangYHe @xzan8189 😄
same, anyone got a solution for this ?
Googling the issue suggests changing the - uses: actions/checkout@v2
to v3 - uses: actions/checkout@v3
I tried it but it didn't change the problem.
@jamesgeorge007 seems to also be getting the warning in the action builds but his actions still build successfully.
So the question arises is there some way to ignore warnings?
After some research I didn't find much more than a flag for something similar but instead for errors not for warnings
https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepscontinue-on-error
but James doesn't seem to be using any flags, so I thought there might be some form of setting that can be changed.
from github-activity-readme.
A more granular approach is adding contents: write
, like this:
jobs:
build:
runs-on: ubuntu-latest
name: Update this repo's README with recent activity
permissions:
contents: write
steps:
- uses: actions/checkout@v2
- uses: jamesgeorge007/github-activity-readme@master
That way, the default permissions don't need to be changed.
from github-activity-readme.
Please follow the advice given by @DorielRivalet. We just recently updated the official README to make users aware of the permissions feature.
from github-activity-readme.
It gives me the same error
from github-activity-readme.
Thank you!
Edit:
Solution
So I did just look around the settings within the actions settings and found the setting that did the trick for me
- Go to your repository's
Settings
tab.- Now on the left side nav bar under the category
Code and automation
click on theActions
dropdown button and select the optionGeneral
- Now scroll down in your page to the
Workflow permissions
here you should find 2 radio buttons, and a checkbox in the bottom, if you haven't made any changes here before your default radio button setting should be the second, namelyRead repository contents and packages permissions
, this setting prevents your action workflows from applying any changes to your repository's files. To change that simply select the radio button option above, namelyRead and write permissions
. Don't forget to click theSave
button in the end, which can be found in the bottom of theWorkflow permissions
section.
I hope this helps you gents @ZhangYHe @xzan8189 😄
same, anyone got a solution for this ? Googling the issue suggests changing the- uses: actions/checkout@v2
to v3- uses: actions/checkout@v3
I tried it but it didn't change the problem. @jamesgeorge007 seems to also be getting the warning in the action builds but his actions still build successfully. So the question arises is there some way to ignore warnings?
After some research I didn't find much more than a flag for something similar but instead for errors not for warnings https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepscontinue-on-error but James doesn't seem to be using any flags, so I thought there might be some form of setting that can be changed.
from github-activity-readme.
Thank you!
Edit:
Solution
So I did just look around the settings within the actions settings and found the setting that did the trick for me
- Go to your repository's
Settings
tab.- Now on the left side nav bar under the category
Code and automation
click on theActions
dropdown button and select the optionGeneral
- Now scroll down in your page to the
Workflow permissions
here you should find 2 radio buttons, and a checkbox in the bottom, if you haven't made any changes here before your default radio button setting should be the second, namelyRead repository contents and packages permissions
, this setting prevents your action workflows from applying any changes to your repository's files. To change that simply select the radio button option above, namelyRead and write permissions
. Don't forget to click theSave
button in the end, which can be found in the bottom of theWorkflow permissions
section.
I hope this helps you gents @ZhangYHe @xzan8189 😄
same, anyone got a solution for this ? Googling the issue suggests changing the- uses: actions/checkout@v2
to v3- uses: actions/checkout@v3
I tried it but it didn't change the problem. @jamesgeorge007 seems to also be getting the warning in the action builds but his actions still build successfully. So the question arises is there some way to ignore warnings?
After some research I didn't find much more than a flag for something similar but instead for errors not for warnings https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepscontinue-on-error but James doesn't seem to be using any flags, so I thought there might be some form of setting that can be changed.
Hi @dimitriosxmi, thank you for your help!
from github-activity-readme.
Related Issues (20)
- Make an empty commit if 50 days have elapsed since the last commit HOT 5
- [ Feature ] Display the date at which the activity happened HOT 3
- Automatically commit re-generated build files on PR push events HOT 4
- `GH_USERNAME` input param is not documented HOT 4
- Support for multiple GH_USERNAME HOT 4
- Actions failing abruptly on upstream repo HOT 2
- My github profile is not updated HOT 2
- Event `undefined` is not supported by this action. HOT 1
- my workflow for recent activity is not working. HOT 11
- option to limit listed events such as PRs
- Support private events in the future? HOT 1
- The action is valid, but the info is not displayed HOT 1
- Is this repository still maintained HOT 1
- [Error] fatal: Error: Invalid status code: 1 HOT 5
- fatal: No PullRequest/Issue/IssueComment events found HOT 1
- ReadMe update failing HOT 7
- Not able to find README.md file HOT 2
- Looking for maintainers HOT 3
- The URL generated for `releaseEvent` is invalid HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from github-activity-readme.