microsoft / microsoft/finops-toolkit

Validate GitHub automation

Open
#55 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Help wanted ✨ Skill: DevOps
Dominant language
PowerShell
Stars
603
Forks
248
Avg merge
7d 11h
Merged PRs (30d)
11

Description

Issues

  • 1. #Triage when new issues are created -- open issue !#Information !#Spec in progress !#Spec review !#Ready !#In progress !#Code review !assigned > #Triage @flanakin
  • 2. #Triage > #Info when comment includes "#needs-info" in a comment -- open issue "#needs-info" comment from @ankur-ms/@flanakin/@tsilvers-ms > #Info -#Triage @author
  • 2a1. +#Attention when no activity -- @1am: open issues inactive for 14d #Info -Attention > #Attention + reply
  • 2b. -#Attention when activity -- issue comment #Attention > -#Attention
  • 2a2. #Attention > Close when no activity -- @1am: open issues inactive for 14d #Info #Attention > Close #NoActivity + reply
  • 2b1. #Duplicate > Close when no activity -- @1am: open issues inactive for 7d #Duplicate > Close + reply
  • 3. #Info > #Triage when author comments -- open issue comment from author #Info > -#Info #Triage @flanakin
  • 4. -#Triage when "#approved" comment -- open issue "#approved" comment from @ankur-ms/@flanakin/@tsilvers-ms #Triage > -#Triage @none
    - [ ] No tags
    - [ ] "#ADF" > #Data factory
    - [ ] "#ARM" > #ARM
    - [ ] "#PBI" > #Power BI
  • 6. #Spec in progress > #Spec review when "Spec review:" PR created -- open issues #Spec in progress +#Spec review > -#Spec in progress
  • 7. #Spec review > #Ready when "Spec review:" PR closes -- open issues #Spec review +#Ready > -Spec review
  • 8. #Ready > #In progress when dev assigned -- open issues #Ready @ankur-ms/tsilvers-ms > -#Ready #In progress
  • 9. #In progress > #Code review when dev creates PR -- new PR #In progress > issue+#Code review +#(copy Area|Breaking|GFI|HW|Micro|Type from issue)
    -- Issues #In progress +#Code review > -#In progress
  • 10. #Code review > #Pending release when PR closes linked issue -- open issues closed #Code review > -#Code review #Pending release
  • 11. #Pending release > #Released when issue is included in a release -- closed issue "Released in v" comment #Pending release > -#Pending release #Released

Pull requests

  • 1. (New) > #Review when opened -- new/updated PR =main > #Review @ankur-ms @tsilvers-ms @flanakin +reviewers
  • 3a. #Attenton > #Review when PR updated -- author updated PR #Attention > -#Attention #Review
  • 3c. #Attenton > #Review when PR comment updated -- author PR comment #Attention > -#Attention #Review
  • 4. #Review > Close???

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Use the checklist in issue #55 as the test plan; the payload names no files, tests, or entry points, so begin by locating the repository's GitHub automation and reproducing the listed issue and pull-request scenarios. Done means each listed label, assignment, comment, inactivity, PR, and release transition behaves as specified.

Written by the indexing model from the issue text.

Assessment

Tech stack
powershell
Domain
ci-cd, devops
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.