issues
search
dotnet
/
fabricbot-config
Scripts for managing fabricbot configurations in the dotnet repos
MIT License
4
stars
7
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
Testing - Automatically moving into triage column
#40
jeffhandley
closed
2 years ago
2
Testing PR Automation
#39
jeffhandley
closed
2 years ago
0
Testing issue automation
#38
jeffhandley
closed
2 years ago
0
Onboard the roslyn-analyzers repo with a Libraries Analyzers pod
#37
jeffhandley
closed
2 years ago
0
Standardize ordering of config settings for easier reviewing. Improve JSON formatting consistency.
#36
jeffhandley
closed
2 years ago
0
Refactor PR champion assignment to address race condition
#35
jeffhandley
closed
2 years ago
0
Only move into a pod member's triage column if the issue is not triaged
#34
jeffhandley
closed
2 years ago
0
Testing issue automation
#33
jeffhandley
closed
2 years ago
3
Move cards into pod members' columns automatically
#32
jeffhandley
closed
2 years ago
1
Testing new untriaged/triaged behavior
#31
jeffhandley
closed
2 years ago
0
Testing new untriaged/triaged behavior
#30
jeffhandley
closed
2 years ago
0
Testing new untriaged/triaged behavior [no milestone]
#29
jeffhandley
closed
2 years ago
4
More Triaged/Untriaged and PR Done automation
#28
jeffhandley
closed
2 years ago
0
Automatically remove untriaged label across all dotnet/runtime areas
#27
jeffhandley
closed
2 years ago
5
Do not add closed PRs to the Needs Champion column
#26
jeffhandley
closed
2 years ago
1
Testing fix of #6 via #24
#25
jeffhandley
closed
2 years ago
9
Only resurrect issue cards if the comment author has (at most) Read permission
#24
jeffhandley
closed
2 years ago
0
Test issue -- Attempt to repro #6
#23
jeffhandley
closed
2 years ago
23
FabricBot config: Viktor is back
#22
jeffhandley
closed
2 years ago
0
Onboard roslyn-analyzers repo for area pod boards
#21
jeffhandley
closed
2 years ago
1
Closing an issue results in double automation of moving the issue to Triaged
#20
jeffhandley
closed
2 years ago
3
Fix problem for Moved to Another Area for issues too
#19
joperezr
closed
2 years ago
0
Fixing issue where PRs added to all boards incorrectly
#18
joperezr
closed
2 years ago
0
Disable the champion assigned and triage started tasks while bugs are addressed
#17
jeffhandley
closed
2 years ago
0
Treat issue comments as triage engagement to move into triager column
#16
jeffhandley
closed
2 years ago
0
Automatically move into triager column when a pod member acts on an issue
#15
jeffhandley
closed
2 years ago
2
Automatically move PRs to champion columns when assigned
#14
jeffhandley
closed
2 years ago
0
Replicate issue/pr tasks from dotnet/runtime; apply them here and to machinelearning
#13
jeffhandley
closed
2 years ago
0
Test issue: Should be marked as untriaged
#12
jeffhandley
closed
2 years ago
2
Introduce issueLabelTasks concept to implement untriaged label feature
#11
jeffhandley
closed
2 years ago
0
Use fabricbot to automatically apply untriaged label when issues are created
#10
jeffhandley
closed
2 years ago
0
Fix: Archived issues are not resurrected into Needs Triage column
#9
jeffhandley
closed
2 years ago
0
Determine how we want to track issues and PRs in auxiliary repositories
#8
jeffhandley
opened
2 years ago
8
Automatically move engaged issues into triage columns
#7
jeffhandley
closed
2 years ago
4
Issues receiving team comments are showing up in the Needs Triage column
#6
jeffhandley
closed
2 years ago
3
Closed PRs are showing up in the Needs Champion column
#5
jeffhandley
closed
2 years ago
1
Archived issues are not resurrected into Needs Triage column
#4
jeffhandley
closed
2 years ago
2
Automatically move assigned PRs into champion columns
#3
jeffhandley
closed
2 years ago
1
Label untriaged should get automatically removed when an issue is triaged
#2
jeffhandley
closed
2 years ago
1
Label needs-author-action is not getting automatically applied/removed in machinelearning
#1
jeffhandley
closed
2 years ago
1
Previous