Skip to content

latest is reactivated on commit #4672

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

Closed
davidism opened this issue Sep 28, 2018 · 4 comments
Closed

latest is reactivated on commit #4672

davidism opened this issue Sep 28, 2018 · 4 comments
Labels
Bug A bug

Comments

@davidism
Copy link

I've disabled the "latest" version. However, every time I push a commit to master, the version is reactivated on RTD. I'd like for the version to stay disabled even on new commits.

@stsewd stsewd added the Bug A bug label Sep 28, 2018
@stsewd
Copy link
Member

stsewd commented Sep 28, 2018

I was able to replicate this on the .org site

@stsewd
Copy link
Member

stsewd commented Sep 28, 2018

I guess this only happens via webhooks, as master is latest, then rtd builds that branch and activates latest.

@stsewd
Copy link
Member

stsewd commented Oct 4, 2018

The code that is changing the active attr is

https://github.com/rtfd/readthedocs.org/blob/35695d170ec7e1dfa2553bf70bc406e7c960409a/readthedocs/core/views/hooks.py#L40-L45

(here slug is master, but it triggers a build to latest)

I'll continue investigating why we are triggering a build to latest there, it may be a bug or some weird design.

@stsewd
Copy link
Member

stsewd commented Oct 4, 2018

I think I understand why we are doing that, we should validate that the version is active first

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug A bug
Projects
None yet
Development

No branches or pull requests

2 participants