Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

ci: add dispatch workflow to update docs website #1024

Closed
wants to merge 4 commits into from

Conversation

fzipi
Copy link
Member

@fzipi fzipi commented Mar 25, 2024

what

  • add dispatch workflow to trigger documentation updates on the website

why

  • adding automation to a manual process

references

Signed-off-by: Felipe Zipitria <felipe.zipitria@owasp.org>
@fzipi fzipi requested a review from a team as a code owner March 25, 2024 12:31
@fzipi fzipi added the chore label Mar 25, 2024
@fzipi fzipi marked this pull request as draft March 25, 2024 12:32
Signed-off-by: Felipe Zipitria <felipe.zipitria@owasp.org>
@fzipi fzipi marked this pull request as ready for review March 25, 2024 13:09
@jcchavezs
Copy link
Member

Thanks for this @fzipi I am not sure about this repo pinging the other to run the deploy. I was more thinking of a dispatch job in the coraza.io where you could specify the coraza hash to run the job. I would invite others to comment whether this is the concern of this repo or not cc @anuraaga @M4tteoP @jptosso

@anuraaga
Copy link
Contributor

If the goal is to make sure every commit gets directly published, this seems OK. Otherwise, I would just use a scheduled_dispatch in the coraza.io repo to update nightly or hourly.

@fzipi
Copy link
Member Author

fzipi commented May 7, 2024

If there are doubts, we close and move the dialog to the other repo 🤷

@fzipi fzipi closed this May 7, 2024
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants