-
Notifications
You must be signed in to change notification settings - Fork 8
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
doc+ci: match ci and style with epipredict/epidatr #418
Conversation
* update with fixes from epidatr * update pull request template * bugfix pkgdown.yaml * add workflow_dispatch buttons to most actions * remove release_helper.yaml which we don't use * update the DEVELOPMENT.md guide with a release checklist * update pkgdown.yaml to match epidatr
Currently tagged: was that intentional, or is the robot set up to tag the wrong people? |
I guess its worth noting that the pkgdown is hopefully temporary until this PR is merged. Though |
Given the amount of outstanding PRs on that repo and last release in 2022, I'm not holding my breath for a quick merge. There's no robo tagging on this repo and I just tagged you because you reviewed the other PR already. |
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.
Matches what we did in epidatr. Might want to wait to see if others want to comment on the process before merging.
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.
Very nice. Mostly asking for some extra details in some of the development docs but have some random other comments.
Co-authored-by: brookslogan <[email protected]>
Co-authored-by: brookslogan <[email protected]>
* also simplify the target_ref calculation
ci: add document, lint, style like epidatr
@brookslogan I fixed a lot of linter unhappiness. |
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.
One other potential color thing. Possibly challenging, but mentioned in cmu-delphi/epipredict#289.
we could fix the search bar pretty quickly by switching off of cosmo- was there some reason we chose that? |
I don't think so. Probably just a function of me not understanding the details of the bootstrap5 functionality. |
I prefer the white search bar over the black one when the background for everything else is white. (Assuming text is visible when you type there.) |
Agreed. I like the white one much better. |
Checklist
Please:
brookslogan, nmdefries.
DESCRIPTION
andNEWS.md
.Always increment the patch version number (the third number), unless you are
making a release PR from dev to main, in which case increment the minor
version number (the second number).
(backwards-incompatible changes to the documented interface) are noted.
Collect the changes under the next release number (e.g. if you are on
0.7.2, then write your changes under the 0.8 heading).
Change explanations for reviewer
Match with
Contains #425
Magic GitHub syntax to mark associated Issue(s) as resolved when this is merged into the default branch