-
Notifications
You must be signed in to change notification settings - Fork 201
Update harness-platform-faqs.md #7110
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
Conversation
|
The build has been failing repeatedly. I have tried adding code ticks to ignore the variable and consider it as code snippets. Cause: Unexpected character |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@saifeemustafaqharness If you commit these suggestions, the build should be successful.
For example: `<+pipeline.variables.get("this-var")>` | ||
|
||
|
||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For example: `<+pipeline.variables.get("this-var")>` | |
For example: `<+pipeline.variables.get("this-var")>` |
Co-authored-by: brian-f <brian.fisher@harness.io>
Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://667961f9cf35c4b16398f4ae--harness-developer.netlify.app |
@saifeemustafaqharness The build is fixed now. After you make any necessary copy edits and move the questions to the applicable categories, I'll re-review and then you can merge the PR. |
This pull request has been automatically closed due to 30 days of inactivity. If you believe this was done in error, please feel free to reopen the PR or reach out to the BT team for further assistance. Thank you for your contributions! |
Thanks for contributing to the Harness Developer Hub! Our code owners will review your submission.
Description
PR lifecycle
We aim to merge PRs within one week or less, but delays happen sometimes.
If your PR is open longer than two weeks without any human activity, please tag a code owner in a comment.
PRs must meet these requirements to be merged: