issues
search
matrix-org
/
mscbot-python
mscbot github bot implementation in python
Apache License 2.0
6
stars
2
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
Add release notes and CI
#37
anoadragon453
opened
2 months ago
0
Bot claimed concerns were unknown upon trying to resolve them
#36
turt2live
opened
8 months ago
0
Announcement in rooms doesn't specify what kind of FCP was proposed
#35
turt2live
opened
1 year ago
1
The bot cleared FCP votes after a concern was raised
#34
anoadragon453
opened
1 year ago
0
Add a little FCP to-do list to the tickyboxes comment
#33
anoadragon453
opened
1 year ago
2
FCP can be started again after one had successfully completed
#32
anoadragon453
opened
1 year ago
1
Raising multiple concerns in a single review races
#31
turt2live
opened
1 year ago
0
Users (who aren't whitelisted) who post top-level to an proposal should have their comment automatically moved to a PR review comment
#30
anoadragon453
opened
1 year ago
1
Inform requesters that they likely forgot to add a path if they hit `https://<webhook_url>/`
#29
anoadragon453
closed
2 years ago
0
Support an FCP call which requires Guardian review
#28
turt2live
opened
2 years ago
0
Remove support for the `proposal-in-review` label
#27
anoadragon453
opened
2 years ago
0
Support @mscbot commands in PR review bodies
#26
anoadragon453
closed
2 years ago
1
Add matrix-org/spec-core-team as a universal codeowner
#25
anoadragon453
closed
2 years ago
0
Move linting dependencies to setup.py and add linting instructions to README
#24
anoadragon453
closed
2 years ago
0
Include the time for the FCP to end in final comment period comment.
#23
clokep
closed
2 years ago
3
The `unresolved-concerns` label should be removed from an MSC if FCP is cancelled
#22
anoadragon453
opened
2 years ago
0
Track a remote branch for an MSC
#21
ShadowJonathan
opened
2 years ago
3
MSC Multi-Authoring
#20
ShadowJonathan
opened
2 years ago
0
mscbot may not start FCP when using `@mscbot reviewed`
#19
anoadragon453
opened
2 years ago
0
Include when an FCP will complete in the comment denoting FCP
#18
clokep
closed
2 years ago
1
Link to comment that raised a concern in the FCP comment
#17
turt2live
opened
3 years ago
0
Concerns should link to the comment in which they were raised
#16
turt2live
opened
3 years ago
0
Have the bot react to commands that don't warrant a comment reply
#15
anoadragon453
opened
3 years ago
0
The bot forgot to add a disposition after a FCP shuffle
#14
anoadragon453
opened
3 years ago
0
Remove the unresolved-concerns label when an FCP is cancelled
#13
anoadragon453
opened
3 years ago
0
Add Concern Label when there's an outstanding concern
#12
anoadragon453
closed
3 years ago
1
Add link to FCP comment to Issue/PR description when an FCP is called
#11
anoadragon453
opened
3 years ago
0
Handling of proposal-in-review and disposition-* labels
#10
anoadragon453
closed
4 years ago
2
Allow cancelling FCP proposed state with 'fcp cancel'
#9
anoadragon453
closed
4 years ago
1
Updating status comments overwrites the original FCP proposal author
#8
anoadragon453
closed
4 years ago
1
Have `fcp cancel` command clear the current FCP proposal
#7
anoadragon453
closed
4 years ago
0
Support for writing and parsing FCP concerns with comment links
#6
anoadragon453
closed
2 years ago
1
Remove proposal-in-review label after FCP completes
#5
anoadragon453
closed
4 years ago
1
Support putting commands in pull request review comments
#4
anoadragon453
closed
4 years ago
1
When a concern is raised during FCP, pause FCP and reset FCP timer
#3
anoadragon453
opened
4 years ago
4
Make Docker image work
#2
benbz
closed
4 years ago
0
Store FCP timer information in the :bell: comment instead of a JSON file
#1
anoadragon453
closed
2 years ago
2