Stepsize Documentation
Home
  • 🏠 Welcome to the Stepsize Docs
  • 🧠Getting Started
    • Getting started with Stepsize
    • Creating your first issue
  • 🏷️Issues
    • How to create an issue
    • Adding more code and context to your issues
    • How to view inline annotations
    • Converting TODOs into issues
    • How to resolve issues
  • πŸ‘₯Team & Collaborators
    • How to invite collaborators
    • Setting up Stepsize for your team
    • Using Stepsize as a Team
    • Talking to your Team Lead about Stepsize
    • Talking to your Head of Engineering about Stepsize
    • Talking to your Product Manager about Stepsize
  • 🏁Workflows
    • Using Stepsize in your planning process
    • Using Stepsize in your code review process
  • 😎Talk to us
    • Contact Us
Powered by GitBook
On this page
  • Setting up the GitHub integration
  • Surfacing tech debt in pull requests
  • Surfacing TODOs and FIXMEs in pull requests
  • What next?
  • Set up a call with us πŸ€™
  1. Workflows

Using Stepsize in your code review process

PreviousUsing Stepsize in your planning processNextContact Us

Last updated 2 years ago

Stepsize provides powerful tools to help your team perform better, faster code reviews.

Setting up the GitHub integration

Our GitHub integration allows you to report tech debt from your pull requests. You can also create GitHub issues from Stepsize issues.

  1. Open the

  2. Integrations > GitHub > Connect your GitHub account

Surfacing tech debt in pull requests

Our pull request tool automatically surfaces issues which relate to the code in the pull request.

This allows the authors and reviewers to assess the potential impact of tech debt on the pushed code.

Your team can also use this to prompt discussion on what tech debt to prioritise for fixing.

Surfacing TODOs and FIXMEs in pull requests

TODOs are a great single-player tool, but a terrible multiplayer tool. When TODOs make it to main, you end up with a never-ending, invisible backlog which isn’t actionable.

Use TODOs to aid your personal code development process. Never merge TODOs into main.

Use Stepsize in pull requests to surface TODOs.

You can create issues from pull requests.

Start your comment with [stepsize] to create an issue from a diff.

The issue will be automatically linked to the code it relates to, both in your code editor and in the web app.

This is a great way to track any tech debt you find during review that your team doesn’t have time to take care of before merging.

What next?

We help organisations like yours develop industry-leading tech debt management all the time. Can we help?

πŸ€™

🏁
Stepsize web app
Set up a call with us