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.

Sign up for GitHub

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

Jump to bottom

Update values-parity-stg.yaml #213

Merged
merged 2 commits into from
Jul 3, 2023
Merged

Update values-parity-stg.yaml #213

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
0f2b9b0
Update values-parity-stg.yaml
mordamax Jul 3, 2023
beaa181
Update hero.pug
mordamax Jul 3, 2023
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
2 changes: 1 addition & 1 deletion helm/values-parity-stg.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,7 @@ common:
DB_PORT: 5432
CMD_BOT_URL: https://command-bot.parity-stg.parity.io/
PIPELINE_SCRIPTS_REF: monorepo
BOT_PR_COMMENT_MENTION: stgbot
BOT_PR_COMMENT_MENTION: bot
secrets:
ALLOWED_ORGANIZATIONS: ref+vault://kv/gitlab/parity/mirrors/command-bot/devops-parity-stg#ALLOWED_ORGANIZATIONS
APP_ID: ref+vault://kv/gitlab/parity/mirrors/command-bot/devops-parity-stg#APP_ID
Expand Down
12 changes: 10 additions & 2 deletions src/command-configs/help/parts/hero.pug
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,11 +9,19 @@ div.ms-hero.mb-lg
p running custom commands, like:
br
code #{commandStart} command-name -v VAR=value id --argument=1 --argument=2
p to add new command:
br
| Or even multiple commands in one comment:
br
code #{commandStart} clean
br
code #{commandStart} command-name --argument=2
br
code #{commandStart} command-name --argument=3
p To add new command:  
ul
li go to
a(href=config.pipelineScripts.repository) #{config.pipelineScripts.repository}
li add new command and open PR
li read
li read  
a(href="\#link-new-command") how to test new command before merging
li merge. Then after merge PR, it accessible without branch override
Loading