https://pantsbuild.org/ logo
Join Slack
Powered by
My contributions to in-repo docs were merged to `m...
# development
b
My contributions to in-repo docs were merged to 
main
but don't seem to be overwriting the older versions of those pages that were in readme. Does the readme page need to be deleted in order for its in-repo version to take over?
a
doc updates do not appear automatically, they need to be manually pushed by someone — usually @hundreds-father-404
in a pinch, I could do it, but it’s not an automatic process
b
Ah. Would someone please trigger the push? I'm blocked on announcing these until they're on the public site.
a
note that 
main
is docs for a future release of pants, and you’ll need to have the changes cherry-picked to the current release version for them to show up there. Has that been done yet, or do you need that too?
b
In the future, should I make a habit of requesting the docs push when I have a docs PR land on 
main
?
Yep, Eric took care of cherry-picking them.
a
which branches do I need to take care of?
h
2.12 - 2.14. i think you will get an error about missing category and need to manually create the page first for the docs update to work (which is why I've been punting on it, tedious to do)
a
is there a current version readme for 
main
?
b
Is this meta I didn't know to add and can go retcon, or something only you can do?
h
no, 
main
branch from github is ignored. we haven't yet forked 2.15. Benjy pushed back when I forked 2.14 "too early"
Is this meta I didn't know to add and can go retcon, or something only you can do?
it would be a big help if you are able to do. in readme.com's website, you create the page for each version you want. you've already done this, but only on 2.12. Need to add to 2.13 and 2.14
👍 1
a
I’ve added the page to 2.13
and am adding it to 2.14
h
this is only necessary when creating a new page
b
Ah, gotcha. I created the page on readme only because Benjy said it was needed to get a slug for the markdown doc's meta headers. I hadn't been aware that more was needed on the readme side.
h
That was correct what you did: the only missing step was then creating that page on 2.13 and 2.14 as well
b
Can't wait to be out of this awkward transitional state where we still have all the constraints of readme holding things back.
Open in Slack
PreviousNext
Powered by