Skip to content

Commit f08b89e

Browse files
authored
fix: highlight the conditions for transferring of an issue (github#16133)
1 parent 30e3aff commit f08b89e

File tree

1 file changed

+5
-1
lines changed

1 file changed

+5
-1
lines changed

content/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,11 @@ shortTitle: Transfer an issue
1717
---
1818
To transfer an open issue to another repository, you must have write access to the repository the issue is in and the repository you're transferring the issue to. For more information, see "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)."
1919

20-
You can only transfer issues between repositories owned by the same user or organization account. {% ifversion fpt or ghes or ghec %}You can't transfer an issue from a private repository to a public repository.{% endif %}
20+
{% note %}
21+
22+
**Note**: You can only transfer issues between repositories owned by the same user or organization account. {% ifversion fpt or ghes or ghec %}A private repository issue cannot be transferred to a public repository.{% endif %}
23+
24+
{% endnote %}
2125

2226
When you transfer an issue, comments, labels and assignees are retained. The issue's milestones are not retained. This issue will stay on any user-owned or organization-wide project boards and be removed from any repository project boards. For more information, see "[About project boards](/articles/about-project-boards)."
2327

0 commit comments

Comments
 (0)