A GitHub plugin and a Codex environment have different roles. One may help inspect issues and pull requests, while coding work needs an appropriate execution environment and repository permissions.
Use a connected repository to investigate and prepare coding work. A concise result with a clear unknown is often the right starting point. Record where the decisive facts came from before acting on them.
Define the task
What to prepare before you begin
Begin with repository, issue, branch, acceptance criteria; then say which source should win if an older copy conflicts with a newer approved one.
A useful deliverable
Reviewable investigation or draft PR. A useful handoff says which items are verified, which are inferred, and which still await a decision.
Worked situation
How this plays out in practice
A repository issue can lead to a draft patch, but opening a pull request, merging, and deploying are distinct stages. Notice how one changed detail alters the judgment. Keep that detail in the brief and inspect whether it survives into the final draft.
Specify the repository, branch, expected behavior, test command, and acceptance criteria. Review the diff and test output before the next action. Record what was tested, what was inferred, and what still needs a person to decide.
A practical sequence
Run a bounded first pass
Collect repository, issue, branch, acceptance criteria and mark any sensitive material that does not need to leave its current place.
Specify repository, branch, issue, expected behavior, and tests. Ask for reproduction notes, a proposed diff, and a draft pull request if supported. Request a preview and a short account of how the source material was interpreted.
Pause where the consequence begins: no merge or deploy by default. A proposal is useful even when the action is postponed.
Editorial judgment
Where a plausible answer can fail
Repository access can include secrets and production workflows. Keep permissions and branch protections explicit. Do not let clean formatting disguise a missing source or a permission the task never received.
Check the diff, CI result, secrets exposure, and target branch before merging. Avoid granting write permissions until required. A useful unresolved list should name the source or person who can answer each question.
Where to go next
Connect this result to the right follow-up
The Apps & Integrations hub gives you the broader route and neighboring tasks. Return there when the present job has produced a result, rather than adding an unrelated responsibility to the same brief. These neighboring pages are useful when the outcome here creates a new question rather than another step in the same job.
For a closely related outcome, open Connect Calendar Apps for Planning. That guide focuses on use a calendar connection for planning with clear edit boundaries. It may use some of the same context, but you should confirm the source and the decision point again. If your next question is about a different angle, Use Dots in Slack is a better fit: use Slack as a way to reach your dot and, separately, as a source for permitted work. A new deliverable should have its own date, owner, and acceptance check.
Before you reuse this result elsewhere, look at Dots Privacy, Memory and Permissions for the wider product or review boundary. Take forward the verified facts and leave behind any assumption that was specific to this example. If the source has changed since the draft was made, update the relevant claim first. The purpose of the link is to make the next step more precise, not to imply that every connected guide is needed for every reader.
Adapt this
Build your own task brief
Edit the bracketed information and any sentence that does not fit your account. This is a suggested workflow, not a promise that your dot has access to a particular app or feature.
Your review
Check before moving on
Tick what you have actually checked. Your progress stays on this device for this page and can be cleared at any time.
0 of 4 checked
Questions
Frequently asked questions
Where should I verify this feature?
Use the scenario on this page as a small test. Specify the repository, branch, expected behavior, test command, and acceptance criteria. Review the diff and test output before the next action. Keep a source and a date beside any detail that can change.
What information matters most for connect github for coding work?
Start with repository, issue, branch, acceptance criteria. A GitHub plugin and a Codex environment have different roles. One may help inspect issues and pull requests, while coding work needs an appropriate execution environment and repository permissions. Give the exact source or account where a decision depends on it.
What changes when a connected app is involved?
Check the diff, CI result, secrets exposure, and target branch before merging. Avoid granting write permissions until required. The relevant access, audience, and consequences determine what you should approve.
What would a useful result look like here?
Reviewable investigation or draft PR. It should make assumptions visible and leave a trail to the source, especially for dates, prices, permissions, or changing product details.
What is the common failure in this situation?
Repository access can include secrets and production workflows. Keep permissions and branch protections explicit. Review that issue in the actual output instead of treating a polished presentation as proof.
Where can I check the current details?
Follow the official source linked below and inspect your account where access matters. This page was revised in October 2026; availability, terms, and product behavior can change.
Source for current product details: official OpenAI documentation or announcement ↗. The worked situations and briefs on this independent site are editorial examples. Confirm current access and details in your account. Editorial policy.