You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, when the deployment is triggered by a doc-site change, we only display the commit sha from the bonita-documentation-site repository.
We could add a prefix like 'site update' and use a short commit sha (as also suggested for #228) and always remove the Deploy prefix which is implicit (this includes deployment triggered by documentation content change).
For instance site update 1d69bc0
We should do the same when triggered manually
current: Deploy ${{github.sha}} from manual request
proposal: site request 1d69bc0
Proposal Summary
The message form will be <source> <type> <short_sha>
For instance
Currently, the message is built by using several steps that are run depending of the availability of some values in the input event and they are written in bash.
The maintenance is not easy and this will be harder with the requirements described in this issue.
We could switch the implementation to JavaScript that allows easy string transforms.
This could be done by using https://github.com/actions/github-script or setting the step shell to shell: node {0}
steps:
- name: Use JavaScript to defined the step contentshell: node {0}run: | // my super JavaScript code here
The text was updated successfully, but these errors were encountered:
tbouffard
changed the title
Improve Netlify deployment message when it is triggered by a doc-site change
Improve Netlify deployment message
Dec 8, 2021
Currently, when the deployment is triggered by a doc-site change, we only display the commit sha from the bonita-documentation-site repository.
We could add a prefix like 'site update' and use a short commit sha (as also suggested for #228) and always remove the
Deploy
prefix which is implicit (this includes deployment triggered by documentation content change).For instance
site update 1d69bc0
We should do the same when triggered manually
Deploy ${{github.sha}} from manual request
site request 1d69bc0
Proposal Summary
The message form will be
<source> <type> <short_sha>
For instance
bonita-2021.2 update 1d69bc0
. Notice that documentation source repository can trigger production deploy with aworkflow_dispatch
as well. If we want the information, it should be passed in therepository_dispatch
event as we want to do for Netlify: track the commit of the documentation content repository that triggers the deploy #228site update 1d69bc0
site request 1d69bc0
orsite manual-request 1d69bc0
Resources for short sha
About the message construction
Currently, the message is built by using several steps that are run depending of the availability of some values in the input event and they are written in bash.
The maintenance is not easy and this will be harder with the requirements described in this issue.
We could switch the implementation to JavaScript that allows easy string transforms.
This could be done by using https://github.com/actions/github-script or setting the step shell to
shell: node {0}
The text was updated successfully, but these errors were encountered: