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

Add workflow for auto updating the website on release #1355

Merged
merged 6 commits into from
Mar 25, 2020
Merged

Add workflow for auto updating the website on release #1355

merged 6 commits into from
Mar 25, 2020

Conversation

Scar26
Copy link
Contributor

@Scar26 Scar26 commented Mar 25, 2020

Fixes: #1337
The bot will have to be granted access to OWASP/www-project-juice-shop/ for this to work

P.S: Just realized the issue is numbered 1337

@J12934
Copy link
Member

J12934 commented Mar 25, 2020

P.S: Just realized the issue is numbered 1337

Noice 😂

@J12934
Copy link
Member

J12934 commented Mar 25, 2020

Btw. if I remember correctly not the bot account needs the rights, but the person doing the push. Which is either the one actually pushing directly to the master branch or the one who clicked the merge button on a PR.

wget https://raw.githubusercontent.com/bkimminich/juice-shop/master/data/static/challenges.yml
- uses: stefanzweifel/git-auto-commit-action@v4.0.0
with:
commit_message: "update challenges.yml after juice-shop release"
Copy link
Member

@J12934 J12934 Mar 25, 2020

Choose a reason for hiding this comment

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

The commit message is currently a bit incorrect as this would actually push on every commit to the master branch (which changes the challenges.yaml). Which happens more frequently than the releases.
Maybe it wold be better to make it run on tags rather than branches?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

No, I added the path property at the beginning so it only activates if changes to challenges.yml have been made

Copy link
Contributor Author

Choose a reason for hiding this comment

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

But should I shift it to tags anyway?

@bkimminich
Copy link
Member

Pushing to master is okay, then it is consistent with the demo Heroku instance. That deploys the master branch, not a tag.

@bkimminich bkimminich changed the base branch from develop to master March 25, 2020 20:24
@bkimminich bkimminich merged commit 01919aa into juice-shop:master Mar 25, 2020
@github-actions github-actions bot locked and limited conversation to collaborators Aug 11, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[⚙️] Copy challenges.yml over to www-project-juice-shop after a release
3 participants