The `unresolved-concerns` label should be removed from an MSC if FCP is cancelled

Open
#22 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
tooling

Research direction

Use the referenced MSC proposal comment as the behavioral example, then inspect the bot's handling of FCP cancellation and the unresolved-concerns label. Confirm how cancellation is detected and where labels are updated; done means cancelling an FCP removes unresolved-concerns from the MSC without affecting other labels.

Written by the indexing model from the issue text.

Description

bug

See for example https://github.com/matrix-org/matrix-spec-proposals/pull/2285#issuecomment-1058496868.

FCP was cancelled, which should nullify concerns. Yet the unresolved-concerns label has been left around.

Dominant language
Python
Stars
7
Forks
2
No merged PRs in 30d

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.

More from matrix-org/mscbot-python

All issues in matrix-org/mscbot-python

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.