Merge pull request #966 from openedx/tcril/fix-gh-org-url

Fix github url strings (org edx -> openedx)

Author: sarina

.editorconfig

@@ -1,5 +1,71 @@
-# This is a file to standardize editor settings: http://EditorConfig.org
-
+# ***************************
+# ** DO NOT EDIT THIS FILE **
+# ***************************
+#
+# This file was generated by edx-lint: https://github.com/openedx/edx-lint
+#
+# If you want to change this file, you have two choices, depending on whether
+# you want to make a local change that applies only to this repo, or whether
+# you want to make a central change that applies to all repos using edx-lint.
+#
+# Note: If your .editorconfig file is simply out-of-date relative to the latest
+# .editorconfig in edx-lint, ensure you have the latest edx-lint installed
+# and then follow the steps for a "LOCAL CHANGE".
+#
+# LOCAL CHANGE:
+#
+# 1. Edit the local .editorconfig_tweaks file to add changes just to this
+#    repo's file.
+#
+# 2. Run:
+#
+#       $ edx_lint write .editorconfig
+#
+# 3. This will modify the local file.  Submit a pull request to get it
+#    checked in so that others will benefit.
+#
+#
+# CENTRAL CHANGE:
+#
+# 1. Edit the .editorconfig file in the edx-lint repo at
+#    https://github.com/openedx/edx-lint/blob/master/edx_lint/files/.editorconfig
+#
+# 2. install the updated version of edx-lint (in edx-lint):
+#
+#       $ pip install .
+#
+# 3. Run (in edx-lint):
+#
+#       $ edx_lint write .editorconfig
+#
+# 4. Make a new version of edx_lint, submit and review a pull request with the
+#    .editorconfig update, and after merging, update the edx-lint version and
+#    publish the new version.
+#
+# 5. In your local repo, install the newer version of edx-lint.
+#
+# 6. Run:
+#
+#       $ edx_lint write .editorconfig
+#
+# 7. This will modify the local file.  Submit a pull request to get it
+#    checked in so that others will benefit.
+#
+#
+#
+#
+#
+# STAY AWAY FROM THIS FILE!
+#
+#
+#
+#
+#
+# SERIOUSLY.
+#
+# ------------------------------
+# Generated by edx-lint version: 5.2.5
+# ------------------------------
 [*]
 end_of_line = lf
 insert_final_newline = true
@@ -11,12 +77,24 @@ trim_trailing_whitespace = true
 
 [{Makefile, *.mk}]
 indent_style = tab
+indent_size = 8
 
-[*.{js,json,yml,yaml}]
+[*.{yml,yaml,json}]
 indent_size = 2
 
-[*.rst]
-max_line_length = 79
+[*.js]
+indent_size = 2
 
 [*.diff]
 trim_trailing_whitespace = false
+
+[.git/*]
+trim_trailing_whitespace = false
+
+[COMMIT_EDITMSG]
+max_line_length = 72
+
+[*.rst]
+max_line_length = 79
+
+# f2f02689fced7a2e0c62c2f9803184114dc2ae4b

.github/workflows/commitlint.yml

@@ -7,4 +7,4 @@ on:
 
 jobs:
   commitlint:
-    uses: edx/.github/.github/workflows/commitlint.yml@master
+    uses: openedx/.github/.github/workflows/commitlint.yml@master

.github/workflows/upgrade-python-requirements.yml

@@ -21,4 +21,4 @@ jobs:
        requirements_bot_github_email: ${{ secrets.REQUIREMENTS_BOT_GITHUB_EMAIL }}
        edx_smtp_username: ${{ secrets.EDX_SMTP_USERNAME }}
        edx_smtp_password: ${{ secrets.EDX_SMTP_PASSWORD }}
-    uses: edx/.github/.github/workflows/upgrade-python-requirements.yml@master
+    uses: openedx/.github/.github/workflows/upgrade-python-requirements.yml@master

README.rst

@@ -7,7 +7,7 @@ platform.  Use it to get up and running quickly with Open edX services.
 Documentation is on `Read the Docs`_.  Code repository is on `GitHub`_.
 
 .. _Read the Docs: https://edx.readthedocs.io/projects/open-edx-devstack/en/latest/
-.. _GitHub: https://github.com/edx/devstack
+.. _GitHub: https://github.com/openedx/devstack
 
 The Devstack runs as multiple containers with `Docker Compose`_ at its core.
 
@@ -339,30 +339,30 @@ Some common service combinations include:
 * ``ecommerce``: Ecommerce, but also LMS as a dependency (for auth)
 * ``studio+credentials``: Services can be combined to affect both at once
 
-.. _credentials: https://github.com/edx/credentials
-.. _discovery: https://github.com/edx/course-discovery
-.. _ecommerce: https://github.com/edx/ecommerce
-.. _edx_notes_api: https://github.com/edx/edx-notes-api
-.. _forum: https://github.com/edx/cs_comments_service
-.. _frontend-app-payment: https://github.com/edx/frontend-app-payment
-.. _frontend-app-publisher: https://github.com/edx/frontend-app-publisher
-.. _frontend-app-gradebook: https://github.com/edx/frontend-app-gradebook
-.. _lms: https://github.com/edx/edx-platform
-.. _frontend-app-program-console: https://github.com/edx/frontend-app-program-console
-.. _registrar: https://github.com/edx/registrar
-.. _studio: https://github.com/edx/edx-platform
-.. _lms: https://github.com/edx/edx-platform
-.. _frontend-app-learning: https://github.com/edx/frontend-app-learning
-.. _frontend-app-library-authoring: https://github.com/edx/frontend-app-library-authoring
-.. _frontend-app-course-authoring: https://github.com/edx/frontend-app-course-authoring
-.. _frontend-app-account: https://github.com/edx/frontend-app-account
+.. _credentials: https://github.com/openedx/credentials
+.. _discovery: https://github.com/openedx/course-discovery
+.. _ecommerce: https://github.com/openedx/ecommerce
+.. _edx_notes_api: https://github.com/openedx/edx-notes-api
+.. _forum: https://github.com/openedx/cs_comments_service
+.. _frontend-app-payment: https://github.com/openedx/frontend-app-payment
+.. _frontend-app-publisher: https://github.com/openedx/frontend-app-publisher
+.. _frontend-app-gradebook: https://github.com/openedx/frontend-app-gradebook
+.. _lms: https://github.com/openedx/edx-platform
+.. _frontend-app-program-console: https://github.com/openedx/frontend-app-program-console
+.. _registrar: https://github.com/openedx/registrar
+.. _studio: https://github.com/openedx/edx-platform
+.. _lms: https://github.com/openedx/edx-platform
+.. _frontend-app-learning: https://github.com/openedx/frontend-app-learning
+.. _frontend-app-library-authoring: https://github.com/openedx/frontend-app-library-authoring
+.. _frontend-app-course-authoring: https://github.com/openedx/frontend-app-course-authoring
+.. _frontend-app-account: https://github.com/openedx/frontend-app-account
 .. _frontend-app-profile: https://github.com/openedx/frontend-app-profile
 .. _frontend-app-authn: https://github.com/openedx/frontend-app-authn
-.. _xqueue: https://github.com/edx/xqueue
-.. _coursegraph: https://github.com/edx/edx-platform/tree/master/openedx/core/djangoapps/coursegraph
+.. _xqueue: https://github.com/openedx/xqueue
+.. _coursegraph: https://github.com/openedx/edx-platform/tree/master/cms/djangoapps/coursegraph#coursegraph-support
 .. _frontend-app-ora-grading: https://github.com/edx/frontend-app-ora-grading
-.. _insights: https://github.com/edx/edx-analytics-dashboard
-.. _analyticsapi: https://github.com/edx/edx-analytics-data-api
+.. _insights: https://github.com/openedx/edx-analytics-dashboard
+.. _analyticsapi: https://github.com/openedx/edx-analytics-data-api
 
 
 Known Issues
@@ -407,18 +407,18 @@ As a specific example, if ``OPENEDX_RELEASE`` is set in your environment as ``ju
 .. _licensing terms: https://www.docker.com/pricing/faq
 .. _Docker for Windows: https://docs.docker.com/docker-for-windows/
 .. _configuring Docker for Mac: https://docs.docker.com/docker-for-mac/#/advanced
-.. _feature added in Docker 17.05: https://github.com/edx/configuration/pull/3864
+.. _feature added in Docker 17.05: https://github.com/openedx/configuration/pull/3864
 .. _edx-e2e-tests README: https://github.com/edx/edx-e2e-tests/#how-to-run-lms-and-studio-tests
 .. _edxops Docker image: https://hub.docker.com/r/edxops/
 .. _Docker Hub: https://hub.docker.com/
 .. _Pycharm Integration documentation: docs/pycharm_integration.rst
 .. _devpi documentation: docs/devpi.rst
-.. _edx-platform testing documentation: https://github.com/edx/edx-platform/blob/master/docs/guides/testing/testing.rst#running-python-unit-tests
-.. |Build Status provisioning| image:: https://github.com/edx/devstack/actions/workflows/provisioning-tests.yml/badge.svg?branch=master
-    :target: https://github.com/edx/devstack/actions/workflows/provisioning-tests.yml
+.. _edx-platform testing documentation: https://github.com/openedx/edx-platform/blob/master/docs/guides/testing/testing.rst#running-python-unit-tests
+.. |Build Status provisioning| image:: https://github.com/openedx/devstack/actions/workflows/provisioning-tests.yml/badge.svg?branch=master
+    :target: https://github.com/openedx/devstack/actions/workflows/provisioning-tests.yml
     :alt: Provisioning tests
-.. |Build Status CLI| image:: https://github.com/edx/devstack/actions/workflows/cli-tests.yml/badge.svg?branch=master
-    :target: https://github.com/edx/devstack/actions/workflows/cli-tests.yml
+.. |Build Status CLI| image:: https://github.com/openedx/devstack/actions/workflows/cli-tests.yml/badge.svg?branch=master
+    :target: https://github.com/openedx/devstack/actions/workflows/cli-tests.yml
     :alt: CLI tests
 .. |docs| image:: https://readthedocs.org/projects/docs/badge/?version=latest
     :alt: Documentation Status

docker-compose.yml

@@ -35,7 +35,7 @@ services:
     container_name: "edx.${COMPOSE_PROJECT_NAME:-devstack}.coursegraph"
     hostname: coursegraph.devstack.edx
     # Try to keep this in sync with the NEO4J_VERSION declared within
-    # https://github.com/edx/configuration/blob/master/playbooks/roles/neo4j
+    # https://github.com/openedx/configuration/blob/master/playbooks/roles/neo4j
     image: neo4j:3.5.28
     networks:
       default:

docs/decisions/0004-backends-depend-on-frontends.rst

@@ -60,7 +60,7 @@ Consequences
 * An email and Slack message will be sent out to explain these changes and how we anticipate that they will impact developer workflows. The email will explain that if a micro-frontend is required to simulate common user story in the default configuration, then that frontend should be devstack, and should be automatically started by the relevant backend using ``depends_on``.
 
 
-.. _documentation in frontend-build: https://github.com/edx/frontend-build#local-module-configuration-for-webpack
+.. _documentation in frontend-build: https://github.com/openedx/frontend-build#local-module-configuration-for-webpack
 .. _ADR 5: ./0005-frontend-package-mounts.rst
 
 Rejected Alternatives

docs/decisions/0005-frontend-package-mounts.rst

@@ -34,7 +34,7 @@ Current SOA: Local packages for frontends
 
 Unfortunately, this flow is currently *not* an option for frontend services (i.e., micro-frontends) when they're run via devstack. This was probably not an intentional omission; frontend services were added to devstack in a somewhat ad-hoc way, and the local-package workflow was probably overlooked.
 
-There is, however, an established strategy for using local packages when running frontends *outside* of devstack. This stategy is described in the `frontend-build documentation <https://github.com/edx/frontend-build#local-module-configuration-for-webpack>`_. Essentially, frontend package respositories can be placed anywhere in the host system, and each frontend's ``module.config.js`` can be pointed at those local respositories using a path relative to the frontend itself. For example:
+There is, however, an established strategy for using local packages when running frontends *outside* of devstack. This stategy is described in the `frontend-build documentation <https://github.com/openedx/frontend-build#local-module-configuration-for-webpack>`_. Essentially, frontend package respositories can be placed anywhere in the host system, and each frontend's ``module.config.js`` can be pointed at those local respositories using a path relative to the frontend itself. For example:
 
 * A frontend dev has ``frontend-app-profile`` within their home folder (``~``).
 * They would like to run a modified version of Paragon, located at ``~/paragon``.
@@ -108,4 +108,4 @@ A more radical alternative would be to explicitly mount certain local frontend p
 
 This approach would have been the most compatible with the existing local frontend package strategy, but it would sharply differ from devstack's backend package strategy.
 
-For reference, here is a draft implementation of this rejected approach: https://github.com/edx/devstack/pull/795.
+For reference, here is a draft implementation of this rejected approach: https://github.com/openedx/devstack/pull/795.

docs/developing_on_named_release_branches.rst

@@ -18,8 +18,8 @@ images until you change or unset ``OPENEDX_RELEASE`` again.  To work on the
 master branches and ``latest`` images, unset ``OPENEDX_RELEASE`` or set it to
 an empty string.
 
-.. _README.rst: https://github.com/edx/devstack
-.. _getting started: https://github.com/edx/devstack#getting-started
+.. _README.rst: https://github.com/openedx/devstack
+.. _getting started: https://github.com/openedx/devstack#getting-started
 
 How do I run multiple named Open edX releases on same machine?
 --------------------------------------------------------------

docs/pycharm_integration.rst

@@ -50,7 +50,7 @@ use the following options:
 - Optional Environment variables:
 
   - ``OPENEDX_RELEASE=release.version`` (i.e.: appropriate image tag; "juniper.master")
-  - ``COMPOSE_PROJECT_NAME=docker-compose.container`` (i.e.: "devstack-juniper.master"; appropriate docker-compose container project for devstack multiple release (same machine); ensures specific Docker containers get used based on release name; Ref: https://github.com/edx/devstack/pull/532)
+  - ``COMPOSE_PROJECT_NAME=docker-compose.container`` (i.e.: "devstack-juniper.master"; appropriate docker-compose container project for devstack multiple release (same machine); ensures specific Docker containers get used based on release name; Ref: https://github.com/openedx/devstack/pull/532)
 
 - Python interpreter path:
 

docs/testing_and_debugging.rst

@@ -118,5 +118,5 @@ and run the tests manually via paver:
 The browser running the tests can be seen and interacted with via VNC as
 described above (Firefox is used by default).
 
-.. _edx-platform testing documentation: https://github.com/edx/edx-platform/blob/master/docs/guides/testing/testing.rst#running-python-unit-tests
+.. _edx-platform testing documentation: https://github.com/openedx/edx-platform/blob/master/docs/guides/testing/testing.rst#running-python-unit-tests
 .. _edx-e2e-tests README: https://github.com/edx/edx-e2e-tests/#how-to-run-lms-and-studio-tests