When should you put a task on a GitHub project?

Add an issue when you want to track the problem beside the code. An issue can hold the expected behavior and the test notes. Put it on a project to see the owner, status and related work.

A pull request is a proposed code change. Review it in the repository. A project can link the work together, and some changes made in the project, such as a new issue assignee, also change the issue.

Who can see the project and the issue?

A project can be public or private. Linked issues and pull requests still require access to the repository they belong to. Check the project role and the underlying repository separately.

GitHub Free lists Issues and Projects. Check whether your other repository needs require a paid plan. Give an outside collaborator only the project and repository access their work needs.

What does a project export contain?

GitHub documents downloading a view as a tab-separated file. Pick the view that contains the work you want. Keep the underlying issue, code links and any discussion you need separately.

A view export gives you a snapshot for a handoff. It is a different task from moving the repository or rebuilding how a project updates.

How can you rehearse a fix handoff?

Draw a fictional workshop booking issue, a project card and a proposed code change. Use no repository or account.

Give the issue one test
Write that a saved booking should still show after a reload.
Give the work an owner
Mark who proposes the fix and who checks it.
Mark the access boundary
Draw a person who can see the project but cannot open the private repository. Do not copy private details to the shared card.