-
Notifications
You must be signed in to change notification settings - Fork 156
Update github checkout action to v5 #639
Description
Intro
This issue has been opened specifically to give 100Devs members a chance to get involved. The issues presented will have more instruction and be easier to solve. If you are already contributing to this project or your skills are well-ahead of this issue, consider letting someone else take this on!
Summary
GitHub actions checkout should be updated to v5. You should be able to test this on your fork, but you may need to contact someone with appropriate permissions to run the actions on the main repo
https://github.com/actions/checkout/releases/tag/v5.0.0
An example of this change from another repo https://github.com/playfulprogramming/playfulprogramming/pull/1389/files
The Task
Creating your branch
- Fork the Together repository.
- Navigate to the development branch using
git checkout development. - Create a new branch using
git checkout -b your-branch-name-here. - If you have questions, more instructions about this can be found in our contributing document.
Setting up a local server
- Execute
npm install - Execute
npm run devin a terminal. - If you get errors, you may have to do one of the following:
- Run
npm ci - Make sure you have a .env file with the necessary secrets
- Run
What you need to do
Update the checkout action versions to v5. They are currently on v4
When you are done
-Use git add . and then git commit -m 'add a descriptive commit message here' to commit your changes to your local branch.
-Push your commit(s) using git push.
-Open your fork in github and you will see a message saying you can create a pull request. Make sure your pull request is pulling into the 'development' branch instead of 'main'.
Other Info
Who to contact
If you have any questions, you can either send a message in the Together channel in 100Devs Discord or contact 20jasper on discord
Relevant file locations
You should be editing the files in .github/workflows
Potential Problems
You may need help from a teammember to trigger the actions to be able to test
If you're interested in working on this feature, please comment so you can be assigned