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

[DOCS] Make example consistent by using .env file #1759

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

wyarde
Copy link

@wyarde wyarde commented Jul 21, 2021

Updated the first example to make use of the .env file to paramterize the version. This I think makes it easier to move on to the second example where this principle is applied.

@cla-checker-service
Copy link

cla-checker-service bot commented Jul 21, 2021

💚 CLA has been signed

@wyarde wyarde force-pushed the use_env_file_consistently branch from f5e5ee8 to 41c9d04 Compare July 21, 2021 14:33
@wyarde wyarde changed the title Make example consistent by using .env file [DOCS] Make example consistent by using .env file Jul 21, 2021
@mergify
Copy link
Contributor

mergify bot commented Feb 24, 2022

This pull request is now in conflict. Could you fix it @wyarde? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch <remote-repo>
git checkout -b use_env_file_consistently <remote-repo>/use_env_file_consistently
git merge <remote-repo>/main
git push <remote-repo> use_env_file_consistently

@mergify
Copy link
Contributor

mergify bot commented Feb 24, 2022

This pull request does not have a backport label. Could you fix it @wyarde? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

  • backport-/d./d is the label to automatically backport to the /d./d branch. /d is the digit
    NOTE: backport-skip has been added to this pull request.

@mergify mergify bot added the backport-skip Skip automated backport with mergify label Feb 24, 2022
@mergify
Copy link
Contributor

mergify bot commented Sep 27, 2022

This pull request is now in conflict. Could you fix it @wyarde? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch <remote-repo>
git checkout -b use_env_file_consistently <remote-repo>/use_env_file_consistently
git merge <remote-repo>/main
git push <remote-repo> use_env_file_consistently

3 similar comments
@mergify
Copy link
Contributor

mergify bot commented Mar 30, 2023

This pull request is now in conflict. Could you fix it @wyarde? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch <remote-repo>
git checkout -b use_env_file_consistently <remote-repo>/use_env_file_consistently
git merge <remote-repo>/main
git push <remote-repo> use_env_file_consistently

@mergify
Copy link
Contributor

mergify bot commented Aug 31, 2023

This pull request is now in conflict. Could you fix it @wyarde? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch <remote-repo>
git checkout -b use_env_file_consistently <remote-repo>/use_env_file_consistently
git merge <remote-repo>/main
git push <remote-repo> use_env_file_consistently

Copy link
Contributor

mergify bot commented Jan 18, 2024

This pull request is now in conflict. Could you fix it @wyarde? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch <remote-repo>
git checkout -b use_env_file_consistently <remote-repo>/use_env_file_consistently
git merge <remote-repo>/main
git push <remote-repo> use_env_file_consistently

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport-skip Skip automated backport with mergify
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant