Skip to content
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

dependabot: monthly updates of github actions #50

Merged
merged 3 commits into from
Apr 5, 2023

Conversation

consideRatio
Copy link
Member

This is one of several PRs opened in the juptyterhub github organization to systematically configure dependabot to update github actions on a monthly basis, for more information see jupyterhub/team-compass#636.

@welcome
Copy link

welcome bot commented Apr 4, 2023

Thanks for submitting your first pull request! You are awesome! 🤗

If you haven't done so already, check out Jupyter's Code of Conduct. Also, please make sure you followed the pull request template, as this will help us review your contribution more quickly.
welcome
You can meet the other Jovyans by joining our Discourse forum. There is also a intro thread there where you can stop by and say Hi! 👋

Welcome to the Jupyter community! 🎉

@GeorgianaElena GeorgianaElena requested a review from Sheila-nk April 5, 2023 08:41
@Sheila-nk
Copy link
Collaborator

LGTM! 🚀 🚀
Thank you @consideRatio for opening this PR!

@consideRatio
Copy link
Member Author

Thanks for reviewing this @Sheila-nk and for your warm encouraging spirit!!! To me it makes a big difference as a contributor, thank you!

Sometimes when I review and approve something, I ask for someone else to review it also before we get something merged - but its a compromise of course since we are time constrainted. If a change is breaking or changing behavior of the projects code or a larger feature being added, I typically request another person to review it as well before merge.

What do you think about following up this approval with a clarification on what you think makes sense to do before a merge, or going for a merge directly? There are guidance on the "when to merge" section from the jupyterhub team compass describing something like that. The same guidance also suggests I could also merge this now with your approval, but not all PR authors has the permissions to do so, so I think its a good practice to avoid using such priviledge.

@Sheila-nk
Copy link
Collaborator

Sheila-nk commented Apr 5, 2023

@consideRatio Oh yes, I apologize! I should have followed up the approval with a merge or a message that you should feel free to merge this PR.

#
# Notes:
# - Status and logs from dependabot are provided at
# https://github.com/jupyterhub/jupyterhub/network/updates.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I just noticed that we might need to make an edit to the link provided for dependabot's status and logs.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah nice catch!!

.github/dependabot.yaml Outdated Show resolved Hide resolved
Co-authored-by: Sheila <114513578+Sheila-nk@users.noreply.github.com>
@Sheila-nk
Copy link
Collaborator

Thank you @consideRatio for your contribution to this repository ❤️
I will now merge this PR 🚀 🚀

@Sheila-nk Sheila-nk merged commit 48c9bac into jupyterhub:main Apr 5, 2023
@welcome
Copy link

welcome bot commented Apr 5, 2023

Congrats on your first merged pull request in this project! 🎉
congrats
Thank you for contributing, we are very proud of you! ❤️

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants