-
Notifications
You must be signed in to change notification settings - Fork 10.1k
[ADD] Recruitment: adding new recruitment flow doc #9616
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
[ADD] Recruitment: adding new recruitment flow doc #9616
Conversation
Hi @Felicious - this is ready for a first-round review! |
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.
Wow, @larm-odoo, I'm really blown away by the thoroughness of this document covering the entire recruitment workflow! Your effort really shines through. 😊
I'm not quite done with my review yet, but I wanted to share some initial thoughts before our meeting tomorrow. Looking forward to collaborating on breaking this use case into several more general pieces of the recruitment workflow!
a62922b
to
e1ab96f
Compare
Hi @Felicious - now that all the other recruitment docs have been added, this is ready for another look! There were a lot of build errors I had to fix to catch this up to the latest version. I think it's in good shape, but as always- your feedback is amazing- so if you have a chance, I'd love another review. |
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.
AMAZING JOB @larm-odoo!
This doc has come a long way after my initial suggestion spawned so many additional PRs. I only had a few very minor suggestions, and I wanted to show my appreciation one more time for taking my suggestions so graciously and seriously to break up the PR into several different docs. The info is much easier to find now, and your attention to detail is commendable!
e1ab96f
to
c14fe38
Compare
Hi @ksc-odoo - this is ready for a final review! |
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.
hey there, @larm-odoo -- just finished my Final Review of this PR. Nice job. There are a decent amount of suggestions/feedback/comments/etc. that require your attention. And I think if you address those, and implement the necessary changes, you can tag me again for another quick look. Thanks! 👍
c14fe38
to
4e8e5cf
Compare
Hi @ksc-odoo - thank you for such a thorough and thoughtful review! I believe I got everything you suggested edited, and answered any questions you had. This is ready for another look! |
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.
hey @larm-odoo -- thanks for making those adjustments. I have another handful of comments/feedback/etc. that require your attention. But, once you make those final adjustments/modifications, you can feel free to tag this for Tech Review. Thanks! 👍
4e8e5cf
to
10af9da
Compare
Hi @samueljlieber - this is ready for a tech review, thanks! |
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.
LGTM, nice job @larm-odoo
Only a nitpick here, can address if you agree.
For a follow-up PR on this doc, consider expanding out the latter stages and also including a section on Stage Automations that would be relevant for recruiters 💪
.....
@robodoo delegate=larm-odoo
10af9da
to
b27be7f
Compare
@robodoo r+ |
Original Recruitment doc too long, breaking off the recruitment flow section into its own doc.
Task Card for this PR.