Skip to content

docs: use a generic repository reference in landing workflow notes #44

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
roodboi wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs: use a generic repository reference in landing workflow notes #44

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/landing-workflow-followups.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ For the current operator-facing workflow, use

This document captures the next layer of work that became obvious while using
`stack` to turn a pile of existing PRs into one verified landing PR in
`TeamSidewinder/event-agent`.
a private application repository.

The current tool is already useful for:

Expand All @@ -32,7 +32,7 @@ parallel, they are the difference between a stack tool and a landing workflow.

## What we learned from a real workflow

The `event-agent` discovery batch looked like this:
The discovery batch looked like this:

- original PRs: `#353`, `#354`, `#363`, `#364`
- intended outcome: one combined landing PR with the verified set
Expand Down
Loading