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

[Action] Project Green Scraper - Integrate Green Scraper GitHub Actions workflow in the TAG ENV repo #403

Open
1 of 3 tasks
guidemetothemoon opened this issue Apr 30, 2024 · 1 comment

Comments

@guidemetothemoon
Copy link
Contributor

Description

Events page that we want to populate data from the Green Scraper tool to will be located in the TAG ENV website events folder in this repository. We would need to integrate the Green Scraper GitHub Actions workflow located in cncf-tags/tag-env-tooling to being triggered on a schedule in the TAG ENV (this) repository.

Outcome

Green Scraper GH Actions workflow is integrated to be triggered on a schedule in the TAG ENV (this) repository.

To-Do

  • Integrate the Green Scraper GitHub Actions workflow located in cncf-tags/tag-env-tooling to being triggered on a schedule in the TAG ENV (this) repository.
  • Define a schedule that the tool will be triggered on. Should be possible to trigger manually, but also once in a few months maybe. TBD.

Code of Conduct

  • I agree to follow this project's Code of Conduct

Comments

No response

@guidemetothemoon
Copy link
Contributor Author

I think that we should be able to use it as a reusable workflow since both repositories are public: https://docs.github.com/en/actions/using-workflows/reusing-workflows#access-to-reusable-workflows
Updating files in the TAG ENV repo should also be relatively easy with reusable workflows.
From the GitHub docs:

If you reuse a workflow from a different repository, any actions in the called workflow run as if they were part of the caller workflow. For example, if the called workflow uses actions/checkout, the action checks out the contents of the repository that hosts the caller workflow, not the called workflow.

Will do a proof of concept on this and confirm.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: In Progress
Development

No branches or pull requests

2 participants