Skip to content

Change CircleCI job title to "Rendered docs" #21423

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

Merged
merged 1 commit into from
Oct 25, 2021

Conversation

timhoffm
Copy link
Member

This was "Check the rendered docs here!" before. None of the other
job names is a full sentence.

@timhoffm timhoffm added this to the v3.5.0 milestone Oct 21, 2021
@QuLogic
Copy link
Member

QuLogic commented Oct 21, 2021

This is on purpose so that it's obvious to find in the list of checks.

@tacaswell
Copy link
Member

On one hand the call to action is nice, on the other hand I see the argument for consistency. I think either is fine.

@timhoffm
Copy link
Member Author

If standing out is the goal, something like *** Rendered docs *** is probably more outstanding.

@story645
Copy link
Member

I liked "Check Rendered Docs" cause the other goal was making this all as obvious as possible to new contributors. While "rendered docs" is pretty obvious, the check is nice as the explicit this is what you do here.

@dstansby
Copy link
Member

dstansby commented Oct 24, 2021

I'm in favour of the "Check the rendered docs here!" too.

@jklymak
Copy link
Member

jklymak commented Oct 24, 2021

If we are wordsmithibg I would go for "check the built docs". "To render" is a pretty technical term in this context whereas "to build" is pretty straightforward. But I also agree that keeping "check" in here is useful for those who are just getting started. Whereas the tests either pass or fail, it is often necessary to check the built docs to make sure they look right. Making it clear where to find them is helpful.

This was "Check the rendered docs here!" before. None of the other
job names is a full sentence.
@timhoffm
Copy link
Member Author

timhoffm commented Oct 24, 2021

Mixing everything together, I ended with "View the built docs". 😄

  • I see the point with the call to action, but "check" feels too much like a mandatory task. "view" is more informative.
  • I see the argument for "built" over "rendered"

@@ -10,4 +10,4 @@ jobs:
repo-token: ${{ secrets.GITHUB_TOKEN }}
artifact-path: 0/doc/build/html/index.html
circleci-jobs: docs-python38
job-title: Check the rendered docs here!
job-title: View the built docs
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
job-title: View the built docs
job-title: View the built docs!

feel like the ! is what makes it really stand out, but like this wording either way.

Copy link
Member Author

Choose a reason for hiding this comment

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

The ! was actually what made me stuble. I find the exclamation mark too strong and a bit offensive here. Viewing the docs is only an offer, not a mandatory or important call to action.

Copy link
Member

@jklymak jklymak Oct 25, 2021

Choose a reason for hiding this comment

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

I think that may be cultural, as I think @story645 maybe meant it in the "have fun!" sort of way. However, even in that sense its a bit informal, and I don't think it helps get the point across, so lets merge this as-is!

Copy link
Member

Choose a reason for hiding this comment

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

Yeah I read/intended the exclamation as a "hey, you can view the docs here!" but totally see how that's a cultural thing so am fine w/ no !

@jklymak jklymak merged commit 79b3232 into matplotlib:main Oct 25, 2021
meeseeksmachine pushed a commit to meeseeksmachine/matplotlib that referenced this pull request Oct 25, 2021
@timhoffm timhoffm deleted the rendered-docs branch October 25, 2021 17:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants