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

Automation of tag-app-delivery repo #566

Open
olivercodes opened this issue Feb 27, 2024 · 3 comments
Open

Automation of tag-app-delivery repo #566

olivercodes opened this issue Feb 27, 2024 · 3 comments
Labels
tag-discuss Items to be reviewed at the next TAG general meeting.

Comments

@olivercodes
Copy link

There is discussion amongst the platforms-wg slack to automate the tag-app-delivery repo. Ideas are to use (one of) Prow, Github Actions, etc. Will update this GH Issue after we talk about it in detail in the WG Meeting.

Note: This carries over the conversation from this slack thread:

https://cloud-native.slack.com/archives/C020RHD43BP/p1707944806442839

@joshgav joshgav added the tag-discuss Items to be reviewed at the next TAG general meeting. label Feb 27, 2024
@olivercodes
Copy link
Author

olivercodes commented Feb 27, 2024

WG Meeting Notes:

Tag wants to use GH Actions
Use this GH Issue to collect requirements and then break out into single action request issues (note, these are probably good-first-issue)

Collect automation needs across the TAG by prompting discussion across the tag

Some ideas mentioned:

  • Action for translation alert, awareness
  • Assignment of issues and prs

@roberthstrand roberthstrand added this to To do in General Business via automation Feb 27, 2024
@abangser
Copy link
Collaborator

abangser commented Mar 2, 2024

I would love to add good first issue label to this one as I think it is concrete and focused for pick up. Do you think we should try to clarify the needed actions more in this issue or create associated issues that are clear and easy to be picked up?

@roberthstrand
Copy link
Collaborator

I would love to add good first issue label to this one as I think it is concrete and focused for pick up. Do you think we should try to clarify the needed actions more in this issue or create associated issues that are clear and easy to be picked up?

Yes, I think opening this up as a good first issue without something more specific would make this harder for people to pick up.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
tag-discuss Items to be reviewed at the next TAG general meeting.
Projects
Development

No branches or pull requests

4 participants