Get recent updates from upstream #1

Add the `environment_variables` field to this serializer that will be returned only when the user is admin.

Update webhook docs

fixed missing apostrophe for possessive "project's"

Fix link in features page

$ for reqs in `ls requirements`; do pur --skip redis,commonmark,django,docker,celery,gitpython,elasticsearch,pyelasticsearch,mercurial --requirement requirements/$reqs; done

https://docs.djangoproject.com/en/2.1/releases/1.11.17/

Reduce logging to sentry

Remove sphinx static and template dir

pyupgrade --py3-plus --py3-only (*.py)

This file is generated by our code and can be used by Python2 when building the documentation, so we need to keep the `u` before the definition of the string.

Upgrade all packages with pur

Filepath can contains non-ASCII characters, so we need to convert to a valid URI before setting it as X-Accel-Redirec NGINX header because only ASCII characters are supported. References, * https://docs.djangoproject.com/en/1.11/ref/unicode/#uri-and-iri-handling * benoitc/gunicorn#1448

$ pre-commit run python-import-sorter --files `find readthedocs -name '*.py'` It was ran with this configuration: readthedocs/common#28

Update docs about contributing to docs

…cs.org into humitos/deprecate-python2

$ pre-commit run --files `find readthedocs -name '*'`

This bot will help us to close issues after requesting more information to the user that reported it.

This bot will help us to clean up our repository and stay with issues that are actionable and we do want to work on them at some point. So, after some inactivity the bot will post a comment and if nobody responds to it, the issue will be closed.

Remove `auto` doctype

Template improvements in "gold/subscription_form.html"

We are using the same 404.html template for 404 errors when serving documentation (.io) and also on our platform (.org). The Login/Logout button only shows the proper word when the 404 page comes from .org, but it always says "Login" when we hit .io 404 pages. As this is only confusing and there is not value added here, I'm removing it completely.

Make $ unselectable in docs

Fix little typo

Remove header nav (Login/Logout button) on 404 pages

…rom-404 Remove unused suggestion block from 404 pages

Convert an IRI path to URI before setting as NGINX header

Install ProBot

Raise exception in failed checkout

Declare and improve invoke tasks

…codes Handle 401, 403 and 404 status codes when hitting GitHub for webhook

…cked-error Add test case for send_notifications on VersionLockedError

Safe symlink on version deletion

* Notify users about the usage of deprecated webhooks Each time a deprecated webhook is hit, a notification is created (without duplicating it) to be sent. * Extend notification to support de-dup and delayed email sent * Improve decorator to support generic and specific VCS webhook views * Remove no necessary settings * DeprecatedWebhookEndpointNotification tests and improvements * Better docstring * Lint * Update copy on notifications for github services deprecation (#5067) * Updated copy on webhooks * Drop "deprecated webhook endpoint" copy, this is core team nomenclature, not user nomenclature. * Add small amount of docs to point to * Update docs and point to docs in notification message * Add year * Split up deprecated view notification to GitHub and other webhook endpoints (#5083) * Updated copy on webhooks * Drop "deprecated webhook endpoint" copy, this is core team nomenclature, not user nomenclature. * Add small amount of docs to point to * Update docs and point to docs in notification message * Split up deprecated view notification to GitHub and other webhook endpoints This sets a date for deprecated of these endpoints as Mar 1st 2019. Too soon? * Reduce complexity and drop decorator pattern for Notification classmethod pattern used in other notifications * Add notifications for non-GitHub incoming webhooks * Add docs as well * More renaming and slight refactor Found out 2x messages are being generated, so this stops the automated mechanism for triggering these messages. * Update dates * Also update docs * Typo on date * Back out some more of the changes to notifications to make them operable without automation * Add admin method for notification * Add admin filter for project features

The progress bar generates too much output, may be the cause of failure in #5093.

The submodule changed and wasn't updated here, so things were broken. I didn't author changes to common, so not sure if everything is safe to bring in.

If any owner of the project is banned, we skip building this project.

Fix common pieces

The tests were trying to match the exact commandlines.

Suppress progress bar of the conda command.

Refactor remove_dir

We are executing python commands like `python /path/to/bin/command` Sometimes it gives a non-deterministic behaviour. Like using pip from the virtualenv in the first build and using pip from the global installation other times. Commands like sphinx-build and mkdocs have an `console_scripts` entry point and shouldn't be a problem.

…etry Fire a signal for domain verification (eg. for SSL)

Use python from virtualenv's bin directory when executing commands

Do not build projects from banned users

CRUD for EnvironmentVariables from Project's admin

Same issue as #5107

Use the python path from virtualenv in Conda

1. `testing` if the project has the feature flag 2. defined by the user in YAML file 3. set by `project.container_image` if an admin override it The image used will be the last one that it's true following that order.

Feature flag to use `readthedocs/build:testing` image

Split requirements/pip.txt

Release 2.8.5

`DOCKER_IMAGE_SETTINGS` has the same value as `env_config`. It is used to update the python version supported for that image.

Check that the repo exists before trying to get a git commit

Make sure that the values we will manipulate from the mkdocs.yml file the correct type we need them to be. If we found a problem with them, we report a proper message to user to debug it by themselves.

Validate mkdocs.yml config on values that we manipulate

Use 2019 in our README

Check for a custom `robots.txt` on the default version and if it does exist serve it. Otherwise, return 404.

Co-Authored-By: humitos <humitos@gmail.com>

Support custom robots.txt

Remove dead code from config module

Update LICENSE

docs: fix integration typos

inv packages.upgrade

Configuration file for ProBot Mergeable Bot

Our docs are currently not building because they depend on the RTD app being installed properly to import strings. This fixes the local-docs-build.txt file to include the proper requirements

pip install -r requirements.txt on a clean installation doesn't install all the requirements. This wasn't detected by travis because we install from requirements/testing.txt pyyaml was a dependency of yamale.

Remove unused validations from v1 config

Fix requirements for local installation

Fix local-docs-build requirements

…/deprecate-python2

Removes `from __future__ import ...`

Co-Authored-By: dojutsu-user <vaibhgupt199@gmail.com>

Upgrade all code to be Python3 only

) This temporarily puts this under a feature flag, to make debugging a little easier, but initial tests show things working as expected. This allows for a large form post to be chunked up and POST, where we were noticing a number of different issues with body size before.

…-verified Display error, using inbuilt notification system, if primary email is not verified

…notification Validate url from webhook notification

Fix the failing domain deletion task

…-search

Added a link to open new issue with prefilled details

This reverts commit 06b07cc.

Upgrade recommonmark to latest and fix integration

Fix Sphinx conf.py inserts

…-search

Upgrade all dependencies

Remove doctype from search

Implement extended install option

Do not list banned projects under /projects/

Use default settings for Config object

SyntaxError caused by comma in python3

Commits on Dec 29, 2018

fix reference

merwok authored Dec 29, 2018

Configuration menu

View commit details

Copy full SHA for 21d43b1

Browse repository at this point

Copy the full SHA

21d43b1 View commit details

Browse the repository at this point in the history

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Get recent updates from upstream #1

Get recent updates from upstream #1

Commits on Dec 27, 2018

Commits on Dec 28, 2018

Commits on Dec 29, 2018

Commits on Jan 1, 2019

Commits on Jan 2, 2019

Commits on Jan 3, 2019

Commits on Jan 4, 2019

Commits on Jan 7, 2019

Commits on Jan 8, 2019

Commits on Jan 9, 2019

Commits on Jan 10, 2019

Commits on Jan 11, 2019

Commits on Jan 12, 2019

Commits on Jan 13, 2019

Commits on Jan 14, 2019

Commits on Jan 15, 2019

Commits on Jan 16, 2019

Commits on Jan 17, 2019

Commits on Jan 18, 2019

Commits on Jan 19, 2019

Commits on Jan 20, 2019

Commits on Jan 21, 2019

Commits on Jan 22, 2019