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.

Sign up for GitHub

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

Jump to bottom

Rename upgrade tests and related resources #1508

Open
TeodorSAP opened this issue Oct 9, 2024 · 2 comments
Open

Rename upgrade tests and related resources #1508

TeodorSAP opened this issue Oct 9, 2024 · 2 comments
Labels
area/tests Writing/adding/Refactoring tests or checks good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. kind/chore Categorizes issue or PR as related to a chore.

Comments

@TeodorSAP
Copy link
Member

Description

We have been using terms such as "lifecycle" or "operational" interchangeably to refer to upgrade tests, and their respective resources. We should just use the term "upgrade" in every such instance, such that:

  • pr-lifecycle GHA, workflow, and jobs should be renamed to pr-upgrade
  • E2E tests label operational should be renamed to upgrade
  • Every other instance or mention of the upgrade tests, should use the "upgrade" term

Reasons

Ensure consistency among the codebase and avoid confusing naming conventions.

Attachments

Release Notes
@TeodorSAP TeodorSAP added kind/chore Categorizes issue or PR as related to a chore. area/tests Writing/adding/Refactoring tests or checks good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. labels Oct 9, 2024
@github-actions GitHub Actions
Copy link

github-actions bot commented Dec 9, 2024

This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs.
Thank you for your contributions.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 9, 2024
@github-actions GitHub Actions
Copy link

This issue has been automatically closed due to the lack of recent activity.
/lifecycle rotten

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Dec 16, 2024
@kyma-bot kyma-bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Dec 16, 2024
@a-thaler a-thaler removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Dec 16, 2024
@a-thaler a-thaler reopened this Dec 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/tests Writing/adding/Refactoring tests or checks good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. kind/chore Categorizes issue or PR as related to a chore.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@a-thaler @kyma-bot @TeodorSAP