Skip to content
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

Can i mark a commit as to skip building the docs? #871

Closed
ankostis opened this issue Aug 5, 2014 · 11 comments · Fixed by #9649
Closed

Can i mark a commit as to skip building the docs? #871

ankostis opened this issue Aug 5, 2014 · 11 comments · Fixed by #9649
Assignees
Labels
Accepted Accepted issue on our roadmap Improvement Minor improvement to code

Comments

@ankostis
Copy link
Contributor

ankostis commented Aug 5, 2014

Is it possible to mark a commit so that readthedocs does not start rebuilding the docs?

TravisCI has this feature: http://docs.travis-ci.com/user/how-to-skip-a-build/#Not-All-Commits-Need-CI-Builds

Front logo Front conversations

@TwoWheelDev
Copy link

This is something I'd very much like to see. There are numerous times when I push a commit but nothing in the docs has needed to be changed.

@ericholscher
Copy link
Member

Neat idea. I'll think more about this.

@ankostis
Copy link
Contributor Author

ankostis commented Aug 6, 2014

For reference here, TravisCI searches the complete commit msg for the string [ci skip] and as a left over the opposite.

@ankostis
Copy link
Contributor Author

ankostis commented Feb 5, 2015

If this gets implemented, it would alleviate some needless burden on the RTD's servers.

By the way, TravisCI supports both these forms: [ci skip] and [skip ci] so i would expect here to be: [rtd skip] and [skip rtd].

@gregmuellegger gregmuellegger added the Improvement Minor improvement to code label Jul 21, 2015
@gregmuellegger
Copy link
Contributor

When we implement it, we should stick to a generic tag like travis is doing (so that more documentation platforms could support it), like [docs skip] and [skip docs].

@humitos
Copy link
Member

humitos commented May 29, 2017

@RichardLitt
Copy link
Member

Looks like the link @humitos provided answers this issue. I'm closing it, for now. Feel free to comment if you need more closure!

@humitos
Copy link
Member

humitos commented Dec 28, 2017

Hehe, my link was just to fix the one that was added to the description (which doesn't point to the correct section) but the feature is not implemented at RTD yet. I'm reopening it.

Sorry about the confusion, I should have explained myself better :)

@humitos humitos reopened this Dec 28, 2017
@agjohnson agjohnson added the Accepted Accepted issue on our roadmap label Sep 19, 2018
@humitos
Copy link
Member

humitos commented Jan 9, 2019

We are not going to implement this for now. We just closed the PR #3457. We can revisit later if we consider. Thank you all!

@humitos humitos closed this as completed Jan 9, 2019
@stsewd
Copy link
Member

stsewd commented Apr 16, 2020

Since we have our new feature for building docs from PRs, we are considering having this feature.

@agjohnson
Copy link
Contributor

Update here: we are currently working on a generic way to expose the ability to skip builds in #9649. Users will be able to define any pattern they like here to skip a build, using build.jobs and build.commands.

@agjohnson agjohnson linked a pull request Oct 22, 2022 that will close this issue
@ericholscher ericholscher moved this to Planned in 📍Roadmap Oct 26, 2022
@ericholscher ericholscher moved this from Planned to In progress in 📍Roadmap Oct 26, 2022
@humitos humitos moved this from In progress to Needs review in 📍Roadmap Nov 8, 2022
@humitos humitos self-assigned this Nov 9, 2022
Repository owner moved this from Needs review to Done in 📍Roadmap Nov 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Accepted Accepted issue on our roadmap Improvement Minor improvement to code
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

9 participants