awesome-notebooks
awesome-notebooks copied to clipboard
Generate contribution certificate when PR is merged
As a contributor, anytime my PR is successfully merged into awesome-notebooks repo, I would like to receive a github notification in the comment that my PR was merged + certificate.
"Thank you for your contribution @slug, your PR has been merged into the master branch of awesome-notebook. Here is the contribution certificate you can share on social media so everybody knows how awesome you are 🤙🌎. Spread the #opensource love 💚" + image of the certificate.
Reference: https://github.com/jupyter-naas/awesome-notebooks/blob/master/Pillow/Pillow_Generate_A_Certificate_Template.ipynb
The idea is to add a generate_certificate.yaml inside the following folder: https://github.com/jupyter-naas/awesome-notebooks/tree/master/.github/workflows
@SuhasBRao maybe you would like to look at this when you created the PR.
Is it something you are comfortable with?
Yes, I will work on it.
Cool 👍 @Dr0p42 can help if you need
I might need help while creating a workflow
no problem, just prepare a PR as you think it should be and @Dr0p42 will check and answer questions based on the PR. The essential point here is to commit your work and try to be as explicit as you can be in the questions 🤙 🔥🔥
no problem, just prepare a PR as you think it should be and @Dr0p42 will check and answer questions based on the PR. The essential point here is to commit your work and try to be as explicit as you can be in the questions 🤙 🔥🔥
@jravenel is there a way to modify variables used in .ipynb using .yaml. To generate a certificate I need to modify certain variables like date_of_contribution, contributor_name etc.
I think it should be a copy of your code from the .ipynb, not the same so you can do what you want
@jravenel I solved it instead of making requests from .py I used API's in .yaml file, Heres the output. Let me know what you think I will create a PR.
Let's go for the PR!! that's awesome man! put @Dr0p42 and myself as reviewer please
@SuhasBRao after discussion internally, we are not going to do it now (not a priority to follow this new process on top of what we are already doing) but we may reopen it later.