chore(ci): add Kanar workflow #PLTM-233 #23
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
quezak
approved these changes
Oct 18, 2024
quezak
approved these changes
Oct 18, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
This change is driven by the company-wide migration from ClickUp to Jira and renaming CliCop to Kanar.
Kanar integrates with Jira, while no longer supporting ClickUp, making introducing Kanar essential for completing the Jira migration.
Intended outcome
Temporarily run Kanar alongside CliCop. We cannot replace CliCop with Kanar immediately, because Github required checks still require
CliCop workflow to run. Once we replace them to expect Kanar workflow instead, we will be free to remove CliCop from CI.
Overview of changes
Quality assurance
If Kanar workflow is green for this PR and detects Jira issue from the title, then it is fine :)