Closed MaxTru closed 3 years ago
Describe the feature / what is the problem?
Once an issue is transferred from a repo to another, it is displayed twice in the wuffle board.
In detail: The original issue URI is still valid (e.g., https://github.com/bpmn-io/fake-join/issues/22) but will redirect to the new issue (https://github.com/bpmn-io/internal-docs/issues/178). The old issue cannot be found in the issues of the original repo (https://github.com/bpmn-io/fake-join/issues/). So it seems like that GitHub simply still provides the reference to the issue on API level.
Probably we need to decide whether this is a bug or a feature. IMO we should filter transferred issues.
Steps to Reproduce
Environment
Apparently there is a transferred event that we do not integrate with, yet: https://docs.github.com/en/free-pro-team@latest/actions/reference/events-that-trigger-workflows
transferred
Describe the feature / what is the problem?
Once an issue is transferred from a repo to another, it is displayed twice in the wuffle board.
In detail: The original issue URI is still valid (e.g., https://github.com/bpmn-io/fake-join/issues/22) but will redirect to the new issue (https://github.com/bpmn-io/internal-docs/issues/178). The old issue cannot be found in the issues of the original repo (https://github.com/bpmn-io/fake-join/issues/). So it seems like that GitHub simply still provides the reference to the issue on API level.
Probably we need to decide whether this is a bug or a feature. IMO we should filter transferred issues.
Steps to Reproduce
Environment