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.

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

Jump to bottom

Update broken link Why run mev-boost? in README #391

Merged
merged 1 commit into from
Nov 2, 2022
Merged

Update broken link Why run mev-boost? in README #391

merged 1 commit into from
Nov 2, 2022

Conversation

franciscodiazydiaz
Copy link
Contributor

@franciscodiazydiaz franciscodiazydiaz commented Nov 1, 2022 •
edited
Loading

📝 Summary

Non-critical change to update a broken link to a writing article (Why run mev-boost?) in the README.

⛱ Motivation and Context

Remove the writings/ path from the URL that returns a 404

$ curl -s -I https://writings.flashbots.net/writings/why-run-mevboost/ | head -n1
HTTP/2 404

$ curl -s -I https://writings.flashbots.net/why-run-mevboost/ | head -n1
HTTP/2 200

✅ I have run these commands

  • make lint
  • make test-race
  • go mod tidy

@jtraglia jtraglia merged commit c4c996d into flashbots:main Nov 2, 2022
screwyprof pushed a commit to screwyprof/mev-boost that referenced this pull request Feb 3, 2023
@franciscodiazydiaz @screwyprof
Update broken link in README (flashbots#391)
0dc9d58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@avalonche avalonche avalonche approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@franciscodiazydiaz @avalonche @jtraglia