Skip to content

Maintenance: remove v1 workflows from v2 before merge #1616

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

Closed
1 of 2 tasks
rubenfonseca opened this issue Oct 19, 2022 · 1 comment · Fixed by #1617
Closed
1 of 2 tasks

Maintenance: remove v1 workflows from v2 before merge #1616

rubenfonseca opened this issue Oct 19, 2022 · 1 comment · Fixed by #1617
Assignees
Labels
internal Maintenance changes v2

Comments

@rubenfonseca
Copy link
Contributor

Summary

We should remove the v1 workflows from the code before merging the v2 code.

Why is this needed?

When we started creating specific workflows for v2, we created separate files. We should now remove the v1 workflows, so they won't interfere with the release process of v2.

Which area does this relate to?

Automation

Solution

No response

Acknowledgment

@rubenfonseca rubenfonseca added triage Pending triage from maintainers internal Maintenance changes and removed triage Pending triage from maintainers labels Oct 19, 2022
@rubenfonseca rubenfonseca self-assigned this Oct 19, 2022
@rubenfonseca rubenfonseca linked a pull request Oct 19, 2022 that will close this issue
7 tasks
@github-actions github-actions bot added the pending-release Fix or implementation already in dev waiting to be released label Oct 19, 2022
@github-actions
Copy link
Contributor

⚠️COMMENT VISIBILITY WARNING⚠️

This issue is now closed. Please be mindful that future comments are hard for our team to see.

If you need more assistance, please either tag a team member or open a new issue that references this one.

If you wish to keep having a conversation with other community members under this issue feel free to do so.

@heitorlessa heitorlessa removed the pending-release Fix or implementation already in dev waiting to be released label Oct 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
internal Maintenance changes v2
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants