Skip to content
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.

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

edit: Pipeline recovery page and update conduit architecture #157

Merged
merged 4 commits into from
Oct 9, 2024

Conversation

raulb
Copy link
Member

@raulb raulb commented Oct 9, 2024

  • Small edits to the existing pipeline recovery page.

@raulb raulb requested a review from a team as a code owner October 9, 2024 10:09
Copy link

cloudflare-workers-and-pages bot commented Oct 9, 2024

Deploying conduit-site with  Cloudflare Pages  Cloudflare Pages

Latest commit: 0c6960d
Status: ✅  Deploy successful!
Preview URL: https://99a0a344.conduit-site.pages.dev
Branch Preview URL: https://raul-pipeline-recovery-chang.conduit-site.pages.dev

View logs

@raulb raulb requested a review from hariso October 9, 2024 10:54
Copy link
Contributor

@hariso hariso left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚀

@hariso hariso merged commit 8e43ea2 into haris/pipeline-recovery Oct 9, 2024
1 check passed
@hariso hariso deleted the raul/pipeline-recovery-changes branch October 9, 2024 10:59
raulb added a commit that referenced this pull request Oct 9, 2024
* Add docs about pipeline recovery

* update

* explain max-retries-window

* explain max-retries-window

* note about default behavior, correct page position

* how to disable

* small fix

* edit: Pipeline recovery page and update conduit architecture (#157)

* update architecture svg

* small edits

* typo

* remove link

---------

Co-authored-by: Raúl Barroso <ra.barroso@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants