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

Add migration mechanism to support "issue re-keying" #171

Closed
jycr opened this issue Apr 12, 2023 · 0 comments · Fixed by #175
Closed

Add migration mechanism to support "issue re-keying" #171

jycr opened this issue Apr 12, 2023 · 0 comments · Fixed by #175
Labels
🏗️ refactoring refactoring for best practices 🗃️ rule rule improvment or rule development or bug 🚀 enhancement New feature or request

Comments

@jycr
Copy link
Contributor

jycr commented Apr 12, 2023 •
edited

Between v1.0.0 and v1.1.0, rule keys have been uniformized.

Older detected issues must be "re-keyed" to new rule key.

Additional information:

Former Repository Key Former Rule Key Current Repository Key Current Rule Key
greencodeinitiative-java GRPS0027 ecocode-java EC27
greencodeinitiative-java S75 ecocode-java EC75
greencodeinitiative-java S74 ecocode-java EC74
greencodeinitiative-java GSCIL ecocode-java EC3
greencodeinitiative-java AMIES ecocode-java EC2
greencodeinitiative-java S77 ecocode-java EC77
greencodeinitiative-java S78 ecocode-java EC78
greencodeinitiative-java GRC1 ecocode-java EC1
greencodeinitiative-java S72 ecocode-java EC72
greencodeinitiative-java SDMLQ1 ecocode-java EC5
greencodeinitiative-java S76 ecocode-java EC76
greencodeinitiative-java D4 ecocode-java EC4
greencodeinitiative-java S79 ecocode-java EC79
greencodeinitiative-java S67 ecocode-java EC67
greencodeinitiative-java GRSP0032 ecocode-java EC32
greencodeinitiative-java S69 ecocode-java EC69
greencodeinitiative-java GRSP0028 ecocode-java EC28
greencodeinitiative-java S63 ecocode-java EC63
greencodeinitiative-java S53 ecocode-java EC53
gci-php S66 ecocode-php EC66
gci-php S74 ecocode-php EC74
gci-php S72 ecocode-php EC72
gci-php S34 ecocode-php EC34
gci-php D4 ecocode-php EC4
gci-php S67 ecocode-php EC67
gci-php S69 ecocode-php EC69
gci-php D2 ecocode-php EC22
gci-python S74 ecocode-python EC74
gci-python D7 ecocode-python EC7
gci-python D4 ecocode-python EC4
gci-python S72 ecocode-python EC72
gci-python S34 ecocode-python EC34
gci-python S69 ecocode-python EC69
jycr added a commit to jycr/ecoCode that referenced this issue Apr 12, 2023
@jycr
green-code-initiative#171 feat: Adds migration mechanism to support "…
ede0d0e 
…issue re-keying"
jycr added a commit to jycr/ecoCode that referenced this issue Apr 12, 2023
@jycr
green-code-initiative#171 feat: Adds migration mechanism to support "…
4763030 
…issue re-keying"
jycr added a commit to jycr/ecoCode that referenced this issue Apr 12, 2023
@jycr
green-code-initiative#171 feat: Adds migration mechanism to support "…
29f682c 
…issue re-keying"
@jycr jycr mentioned this issue Apr 12, 2023
Merged
@dedece35 dedece35 added 🚀 enhancement New feature or request 🗃️ rule rule improvment or rule development or bug 🏗️ refactoring refactoring for best practices labels Apr 13, 2023
@jycr jycr mentioned this issue Apr 14, 2023
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
🏗️ refactoring refactoring for best practices 🗃️ rule rule improvment or rule development or bug 🚀 enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[ISSUE 171] Adds migration mechanism to support "issue re-keying" jycr/ecoCode
2 participants
@jycr @dedece35