FAQ

This page answers common questions that are not covered in detail on other pages.

What if I am stuck?

Ask for help. When asking, see the Troubleshooting page for what to include in your question. Being stuck is normal. Clear questions help others help you faster.

Who reviews pull requests?

Another contributor should review your pull request before it is merged. Reviews help catch bugs, improve readability, and share knowledge across the team. See the Code review page for details.

When can I merge?

Merge after:

• the pull request has been reviewed
• requested changes have been handled
• the linked issue is included in the PR description
• the change has been tested
• the team has approved merging

Do not merge directly to master without review.

What should I do after my pull request is merged?

1. Switch back to master.
2. Pull the latest changes.
3. Delete your old branch.
4. Pick a new issue if you want to continue.

git checkout master
git pull origin master

Should I delete my branch after merge?

Usually, yes. Once the pull request is merged and the branch is no longer needed, it can be deleted. This keeps the repository clean. GitHub may offer a button to do this automatically.

Can I change files outside my issue?

Avoid unrelated changes. If you notice something else that should be fixed, open a separate issue or pull request. This makes review easier and keeps the project history clear.