Readthedocs.org: Branch does not appear

[niden]

Greetings,

We have created a new branch of the documents in our project "1.0.0" and it appears that it is not being picked up by RTD. All the previous branches "0.9.0", "0.8.0" etc. have appeared in the past (and are still there) but the 1.0.0 refuses to do so.

Any pointers are more than appreciated.

Github project: https://github.com/phalcon/docs
RTD: https://readthedocs.org/projects/phalcon-php-framework-documentation/

Thanks!

[ericholscher]

RTD only picks up new tags when the project is built. I noticed you hadn't
built anything in the past day, and triggered a new build. This seems to
have picked up the new version.

On Tue, Feb 12, 2013 at 9:29 AM, Nikolaos Dimopoulos <
[email protected]> wrote:

Greetings,

We have created a new branch of the documents in our project "1.0.0" and
it appears that it is not being picked up by RTD. All the previous branches
"0.9.0", "0.8.0" etc. have appeared in the past (and are still there) but
the 1.0.0 refuses to do so.

Any pointers are more than appreciated.

Github project: https://github.com/phalcon/docs
RTD: https://readthedocs.org/projects/phalcon-php-framework-documentation/

Thanks!

—
Reply to this email directly or view it on GitHubhttps://github.com/rtfd/readthedocs.org/issues/337.

Eric Holscher
Maker of the internet residing in Portland, Or
http://ericholscher.com

[niden]

Hey Eric,

Thank you very much for the prompt reply.

Correct me if I am wrong but shouldn't the creation of a new branch trigger this? and the branch is created, a new push to it should do the same?

I pushed a change not a few minutes ago before I opened the ticket. I suspect that RTD did not pick the new branch somehow when it was created thus was unaware of the relevant push.

Thanks!!

[ericholscher]

Creating a new branch isn't a new commit. I believe github only processes
the post-commit hooks on commits, and not branch or tag creation. We also
do some clever stuff on our end to only build on branches that are already
active in RTD.

On Tue, Feb 12, 2013 at 9:38 AM, Nikolaos Dimopoulos <
[email protected]> wrote:

Hey Eric,

Thank you very much for the prompt reply.

Correct me if I am wrong but shouldn't the creation of a new branch
trigger this? and the branch is created, a new push to it should do the
same?

I pushed a change not a few minutes ago before I opened the ticket. I
suspect that RTD did not pick the new branch somehow when it was created
thus was unaware of the relevant push.

Thanks!!

—
Reply to this email directly or view it on GitHubhttps://github.com/rtfd/readthedocs.org/issues/337#issuecomment-13444980.

Eric Holscher
Maker of the internet residing in Portland, Or
http://ericholscher.com

[ericholscher]

So. I think there are a couple things at play here.

We don't build branches that aren't active on the site. So, when you push a
new branch, we just see it as commits to a branch that isn't active, so a
build doesn't happen.

Assuming you don't also pair this with a normal commit, no build will
happen on RTD, so the new version doesn't get picked up until a new build
happens.

What we should do is kick off a lightweight "update versions" job whenever
we get a post-commit from github about the creation of a new tag or branch
that we don't know about (or a commit to the same). I don't know if github
actually lets us know about branch/tag creation, but we could definitely do
it on a commit to a branch we don't know about.

On Tue, Feb 12, 2013 at 9:39 AM, Eric Holscher [email protected]:

Creating a new branch isn't a new commit. I believe github only processes
the post-commit hooks on commits, and not branch or tag creation. We also
do some clever stuff on our end to only build on branches that are already
active in RTD.

On Tue, Feb 12, 2013 at 9:38 AM, Nikolaos Dimopoulos <
[email protected]> wrote:

Hey Eric,

Thank you very much for the prompt reply.

Correct me if I am wrong but shouldn't the creation of a new branch
trigger this? and the branch is created, a new push to it should do the
same?

I pushed a change not a few minutes ago before I opened the ticket. I
suspect that RTD did not pick the new branch somehow when it was created
thus was unaware of the relevant push.

Thanks!!

—
Reply to this email directly or view it on GitHubhttps://github.com/rtfd/readthedocs.org/issues/337#issuecomment-13444980.

Eric Holscher
Maker of the internet residing in Portland, Or
http://ericholscher.com

Eric Holscher
Maker of the internet residing in Portland, Or
http://ericholscher.com

[iblis17]

Hi,
I also have some problem about branch: I cannot see any branch in the admin panel.

Github project: https://github.com/couchapp/couchapp
I want to add build for branch stable-1.0, but I cannot figure out any way to add it.

[agjohnson]

@iblis17 please create a new issue to track this separate issue, this ticket has been closed for a long time now

[iblis17]

@agjohnson ok. Thanks for your reply!

[pevogam]

I encountered the same issue. I am not sure what is the meaning of creating a new issue and lose all the information already gathered here if it is the same issue in the end. @iblis17 Can you post here a link with your reopened issue then?

[stsewd]

@pevogam I think the this is the issue https://github.com/rtfd/readthedocs.org/issues/2163

[pevogam]

@stsewd Thanks a bunch!

[pllim]

Six years on and https://github.com/rtfd/readthedocs.org/issues/337#issuecomment-13444783 still helped. Thanks!

[stsewd]

@pllim if your project was imported ~2 months ago, it should work, if your project was imported a time ago, you can have this new feature adding new permissions to the github webhook https://docs.readthedocs.io/en/stable/webhooks.html#github

Branch or tag creation, Branch or tag deletion

[williamfgc]

from comment

so the new version doesn't get picked up until a new build
happens.

saved me hours of frustration.

[stsewd]

@williamfgc if you have a webhook setup with the proper permissions, you can get your branches updated on each push. See https://docs.readthedocs.io/en/stable/webhooks.html#webhook-creation

Select Let me select individual events, and mark Branch or tag creation, Branch or tag deletion and Pushes events

[williamfgc]

@stsewd thanks for the follow up. rtd is working great with the new conda env feature. The related issue is that my new branch wasn't appearing (our webhooks are set up so all branches in upstream will be recognized) in the Inactive Versions menu. I was spending time trying several things, but the above line had the answer, a new Build must be triggered from rtd to sync with github for the very first time. After that, it's automatic as expected in your description...saved my day. Thanks for the great work with rtd, the conda env feature is pretty awesome.