-
Notifications
You must be signed in to change notification settings - Fork 701
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
generate doc/requirements.txt #10031
Conversation
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'd expect some updates to documentation. e.g. doc/README.md
. Maybe the Makefile.
Yes, this is still WIP, let me switch it to draft. |
19dcccd
to
aaf052e
Compare
Actually, I'm not sure we want to update the Makefile; it's going to be more necessary with this change, if someone wants to build docs locally. |
7dd9d50
to
2aca7c4
Compare
Okay, the basics now work. Documentation is next (tomorrow, I should go to bed…). |
This is magnificent, the less there is the harder it breaks. Many thanks! |
a4ad174
to
17bc8c1
Compare
First cut at documentation added. |
|
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.
Long awaited improvement, thank you very much!
74c7a40
to
d0205af
Compare
As suggested in haskell#10030 (review)
As suggested in haskell#10030 (review)
d0205af
to
23e9c1a
Compare
The reason this needs to be backported is that backports of subsequent changes to |
@mergify backport 3.12 |
✅ Backports have been created
|
* generate doc/requirements.txt As suggested in #10030 (review) * generate doc/requirements.txt As suggested in #10030 (review) (cherry picked from commit 2658ac6)
* generate doc/requirements.txt As suggested in #10030 (review) * generate doc/requirements.txt As suggested in #10030 (review) (cherry picked from commit 2658ac6)
generate doc/requirements.txt (backport #10031)
* generate doc/requirements.txt As suggested in haskell#10030 (review) * generate doc/requirements.txt As suggested in haskell#10030 (review)
* generate doc/requirements.txt As suggested in haskell#10030 (review) * generate doc/requirements.txt As suggested in haskell#10030 (review)
As suggested in #10030 (review)
Template B: This PR does not modify behaviour or interface
E.g. the PR only touches documentation or tests, does refactorings, etc.
Include the following checklist in your PR: