Docs › Daily use
Daily use for developers
Your day in MCDock: My work, branches, pull requests, reviews, large files and pipelines.
New here? First do the one-time steps in the quick start for engineers.
Start of the day
- Open My work. It lists the pull requests waiting for your review, your own open pull requests, and the issues assigned to you.
- The bell shows mentions, review requests, merges and failed pipelines. Choose bell, e-mail or Teams for each event in your notification settings.
- Update your local copy with
git pull, or fetch in your IDE.
Making a change
- Create a branch from the latest main branch:
git switch -c fix/login-timeout. - Commit small steps with clear messages. Mention an issue with
#123to link it. - Push:
git push -u origin fix/login-timeout. - Open a pull request from the link Git prints, or from the repository page. Add a description and pick reviewers. The CODEOWNERS are added for you.
- Watch the checks on the pull request. If the pipeline fails, open the job to see the live log and the test report.
- When the approvals and checks are in, press Merge, or turn on Merge when ready and move on.
Reviewing someone else's work
- Open the pull request from My work and read the diff. Comment on a line, or on the whole change.
- Approve it, or leave a comment saying what must change. If the author pushes again, old approvals can be dismissed so the new code gets a look too.
- Keep reviews small and quick. A review that waits a day blocks a colleague.
Large files and engineering files
- CAD, PCB, firmware images and other binaries go to Git LFS automatically when the repository was made from a template.
- Lock a file before you edit one that can't be merged:
git lfs lock Parts/bracket.SLDPRT. It unlocks when you push, or withgit lfs unlock. - Look at PDF, STL/OBJ, DXF, Gerber, KiCad and firmware files in the browser without installing anything.
Good habits
- Never commit passwords, keys or tokens. Push protection refuses most of them, but don't rely on it.
- Use a personal access token for Git, with an expiry date. Revoke it under Account → Security when a PC is lost.
- Use Open in to open the repository in your IDE or Git client with one click.
When something goes wrong
- "pre-receive hook declined": a branch rule, a locked file or the secret scanner stopped the push. The message says which one.
- "pushes are paused": the server is in maintenance, low on disk or read-only. Clone and pull still work. Tell your IT administrator.
- Merged something by mistake? Undo it with
git revertin a new pull request. Never force-push a shared branch.
Updated 21 Nov 2026 · Something missing? Ask in the community.