When an issue is raised in an archived (read-only) repository, it is not possible to self-assign or modify the issue. However, all the issue labels might still be applicable, even though no further updates can be made in such repositories.
To resolve this, the bot should automatically close any issue that is reported in an archived repository.[^01^]
Steps to Implement:
Check Repository Status: Identify if the issue is raised in an archived repository.
Close the Issue: If the repository is archived, automatically close the issue while maintaining all the existing labels and comments.
Notification (Optional): Notify the user (or provide a comment) that the issue was closed due to the repository being archived.
This will ensure that issues in archived repositories are properly closed without manual intervention.
Description:
When an issue is raised in an archived (read-only) repository, it is not possible to self-assign or modify the issue. However, all the issue labels might still be applicable, even though no further updates can be made in such repositories.
To resolve this, the bot should automatically close any issue that is reported in an archived repository.[^01^]
Steps to Implement:
Check Repository Status: Identify if the issue is raised in an archived repository. Close the Issue: If the repository is archived, automatically close the issue while maintaining all the existing labels and comments. Notification (Optional): Notify the user (or provide a comment) that the issue was closed due to the repository being archived. This will ensure that issues in archived repositories are properly closed without manual intervention.
[^01^]: ⚠ 86% possible duplicate - Close issues from archived repositories