Skip to content

Update issue transfer documentation#20252

Merged
sophietheking merged 3 commits into
github:mainfrom
anleac:patch-2
Aug 30, 2022
Merged

Update issue transfer documentation#20252
sophietheking merged 3 commits into
github:mainfrom
anleac:patch-2

Conversation

@anleac

@anleac anleac commented Aug 29, 2022 •
edited
Loading

Copy link
Copy Markdown

Why:

This reflects the new default behaviour of issues transfer. Labels are now only transferred if they have a match by name in the target repository, and milestones also will be transferred if they match by both name and due-date, so the documentation should reflect this.

This is also reflected today in the dialogue used for transferring:

image

What's being changed (if available, include any code snippets, screenshots, or gifs):

Check off the following:

  • I have reviewed my changes in staging (look for the "Automatically generated comment" and click the links in the "Preview" column to view your latest changes).
  • For content changes, I have completed the self-review checklist.

Writer impact (This section is for GitHub staff members only):

  • This pull request impacts the contribution experience
    • I have added the 'writer impact' label
    • I have added a description and/or a video demo of the changes below (e.g. a "before and after video")

@welcome

welcome Bot commented Aug 29, 2022

Copy link
Copy Markdown

Thanks for opening this pull request! A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.

@github-actions github-actions Bot added the triage Do not begin working on this issue until triaged by the team label Aug 29, 2022
@github-actions

github-actions Bot commented Aug 29, 2022 •
edited
Loading

Copy link
Copy Markdown
Contributor

Automatically generated comment ℹ️

This comment is automatically generated and will be overwritten every time changes are committed to this branch.

The table contains an overview of files in the content directory that have been changed in this pull request. It's provided to make it easy to review your changes on the staging site. Please note that changes to the data directory will not show up in this table.

Content directory changes

You may find it useful to copy this table into the pull request summary. There you can edit it to share links to important articles or changes and to give a high-level overview of how the changes in your pull request support the overall goals of the pull request.

Source Preview Production What Changed
issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository.md fpt
ghec
ghes@ 3.6 3.5 3.4 3.3 3.2
ghae
 fpt
ghec
ghes@ 3.6 3.5 3.4 3.3 3.2
ghae

fpt: Free, Pro, Team
ghec: GitHub Enterprise Cloud
ghes: GitHub Enterprise Server
ghae: GitHub AE

@cmwilson21

cmwilson21 commented Aug 29, 2022

Copy link
Copy Markdown
Contributor

👋 @anleac Thanks so much for opening a PR! I'll get this triaged for review ⚡

@cmwilson21 cmwilson21 added content This issue or pull request belongs to the Docs Content team waiting for review Issue/PR is waiting for a writer's review issues Content related to issues and removed triage Do not begin working on this issue until triaged by the team labels Aug 29, 2022
@sophietheking sophietheking self-requested a review August 30, 2022 06:28
sophietheking
sophietheking previously approved these changes Aug 30, 2022
View reviewed changes

@sophietheking sophietheking left a comment •
edited
Loading

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @anleac 👋 thanks for opening this PR! Looks good to me, only left one small suggestion for your consideration, but feel free to ignore it if it doesn't make sense to you.

Please feel free to @mention me here and I'll get this merged for you!

Comment thread content/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository.md Outdated
@sophietheking
Update content/issues/tracking-your-work-with-issues/transferring-an-…
1197d90 
…issue-to-another-repository.md

Co-authored-by: Sophie <29382425+sophietheking@users.noreply.github.com>
@anleac

anleac commented Aug 30, 2022

Copy link
Copy Markdown
Author

Hi @anleac 👋 thanks for opening this PR! Looks good to me, only left one small suggestion for your consideration, but feel free to ignore it if it doesn't make sense to you.

Please feel free to @mention me here and I'll get this merged for you!

thanks for that suggestion @sophietheking, it absolutely makes things cleaner. Committed!

@sophietheking sophietheking merged commit 311c115 into github:main Aug 30, 2022
@github-actions

github-actions Bot commented Aug 30, 2022

Copy link
Copy Markdown
Contributor

Thanks very much for contributing! Your pull request has been merged 🎉 You should see your changes appear on the site in approximately 24 hours. If you're looking for your next contribution, check out our help wanted issues ⚡

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@sophietheking sophietheking sophietheking approved these changes

Assignees

No one assigned

Labels

content This issue or pull request belongs to the Docs Content team issues Content related to issues waiting for review Issue/PR is waiting for a writer's review

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@anleac @cmwilson21 @sophietheking