-
-
Notifications
You must be signed in to change notification settings - Fork 5.2k
Clarify how workflow can be injected #14106
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
0a183ab
to
a99fd2b
Compare
@lyrixx good for you ? |
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.
Thanks for your PR. I felt a couple of comment.
Could you also change the PR title, because it does not reflect the PR anymore (the title is used to create the commit message)
018b64c
to
9e10527
Compare
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.
👍🏼
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.
Thank you @epitre
This is great!
Thank you @epitre for your research on this topic and the time you put into sharing your findings with others! This PR is perfect :) |
This PR was submitted for the master branch but it was squashed and merged into the 4.4 branch instead. Discussion ---------- Clarify how workflow can be injected Commits ------- cb1a140 Clarify how workflow can be injected
Fyi, I've merged this PR in the 4.4 version of the docs and I'll bring it in newer version from there. This is why I cannot mark this PR as "merged". But here is the proof that your first doc contribution is a fact: 4cb6b21 :) |
No description provided.