Issues, pull requests & planning

Turn tasks into reviewed changes and keep project work visible.

Track work with issues

Avoid including secrets or private data in public issues. Check repository visibility before attaching logs.

  1. Open a repository’s Issues tab.
  2. Create an issue with the expected behavior, current behavior, and useful reproduction details.
  3. Use the organization tools offered by the issue UI to keep the task discoverable.

Propose a change

  1. Create a working branch, commit your changes, and push it.
  2. Open Pull requests in the repository and start a proposed change.
  3. Select the source and target branches, inspect the diff, and describe the outcome.
  4. Review discussion and checks before using the merge controls available to your role.

Before you continue: Resolve conflicts and follow repository policies. Do not assume that owning a branch automatically grants merge permission.

Organize the project

Use the project board to organize work, discussions for conversations, and the roadmap for planned changes. Use releases for published project milestones. Available controls depend on your role and the repository’s current configuration.

Find work across projects

Use the review inbox, pull-request view, code search, and project updates to move across repositories. Saved items, snippets, and planners provide additional places to organize useful material.

Browse all guides

Ramuvo is in early access. Access and available controls depend on your account and repository role.