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
History.md - add links [skip ci] #2383
Conversation
History.md
Outdated
* Fix `not_token` being able to be set to true ([#1803]) | ||
* Fix "Hang on SIGTERM with ruby 2.6 in clustered mode" ([PR [#1741]], [#1674], [#1720], [#1730], [#1755]) | ||
|
||
[PR [#1741]]: https://github.com/puma/puma/pull/1741 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like this 👍 |
6911188
to
574b5b6
Compare
574b5b6
to
25d13a0
Compare
Sorry, I assumed that the first pass thru it contained no links. Fixed, reformatted some other things, I think it's correct now. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 👍
@MSP-Greg do we expect contributors to make links or will you run your tooling (sounds like you have something) every now and then?
Please, no. That presupposes a knowledge of markdown, etc... I'll work on the tooling, maybe add it to tools/history or something. I may need to add a json file that contains info about every PR and issue, as one never knows how far back they are, especially with issues. Right now, the file is about 450k. It also requires that one has a token to access the GH GraphQL API. Also, the tooling could go in another Puma repo... |
Beautiful! |
Description
Add links to History.md.
Leave the title attribute (date & user)?
I've got code for the first pass, I'll get it working for updates (grabs repo pr/issue info with GraphQL call).
Your checklist for this pull request
[changelog skip]
or[ci skip]
to the pull request title.[ci skip]
to the title of the PR.#issue
" to the PR description or my commit messages.