Skip to content
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions docs/_includes/CONST.html
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
{% if jekyll.environment == "production" %}
{% assign MAIN_SITE_URL = "https://new.expensify.com" %}
{% else %}
{% if jekyll.environment == "development" %}
{% assign MAIN_SITE_URL = "https://dev.new.expensify.com:8082" %}
Comment on lines +1 to 2

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Set JEKYLL_ENV where the deploy build runs

In the inspected deployExpensifyHelp workflow, the production push build at .github/workflows/deployExpensifyHelp.yml:70-72 still runs bundle exec jekyll build without exporting JEKYLL_ENV; with Jekyll's default unset environment being development, this branch still assigns MAIN_SITE_URL to https://dev.new.expensify.com:8082 for deployed help builds. As a result, the generated production help pages continue to send users to the dev Concierge URL instead of https://new.expensify.com/concierge unless the workflow is also changed to set JEKYLL_ENV=production.

Useful? React with 👍 / 👎.

{% else %}
{% assign MAIN_SITE_URL = "https://new.expensify.com" %}
{% endif %}

{% capture CONCIERGE_CHAT_URL %}{{MAIN_SITE_URL}}/concierge{% endcapture %}
Loading