-
Notifications
You must be signed in to change notification settings - Fork 9
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
Chore: Add naming conventions to documentation #189
base: main
Are you sure you want to change the base?
Conversation
c4d9fbe
to
442a7b4
Compare
README.md
Outdated
| --------------- | ---------------- | ---------------------- | | ||
| [GV] | Gerrit (Verify) | gerrit-verify.yaml | | ||
| [GM] | Gerrit (Merge) | gerrit-merge.yaml | | ||
| [G] | Gerrit (Generic) | [either of the above] | |
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.
The Generic
really should be listing a filename that is gerrit-<something>
.yaml as we do technically actually support other types, just nobody is doing so in practice right now. To be specific this would be used for custom magic comment keyword triggers.
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.
I know I'm being a little pedantic, but I would like the idea around the generic
Gerrit workflows to be reworked. See my comment in the file itself.
fd45176
to
ebe5a54
Compare
831ccff
to
f0b51c1
Compare
Signed-off-by: Matthew Watkins <[email protected]>
f0b51c1
to
49f65d3
Compare
| Description | Directory Suffix | | ||
| ----------- | ---------------- | | ||
| Composite | -action | | ||
| Javascript | -javascript | |
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.
To be specific this should be Typescript, not Javascript (related, but not exactly the same)
|
||
Discussion Points (on the table above) | ||
|
||
We could locate deployed workflows in a separate folder structure from |
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.
IIRC workflows must live under the workflows directory even if they're called by another workflow. If I'm not correct, can you point me to documentation or working example of being able to call them from someplace else?
Will pass linting if/when we merge: #188