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

feat: Add a PR template #14

Merged
merged 2 commits into from
Jun 20, 2024
Merged

feat: Add a PR template #14

merged 2 commits into from
Jun 20, 2024

Conversation

gabyx
Copy link
Contributor

@gabyx gabyx commented Jun 19, 2024

Contents

Playing around with some Best-Practices.
Comments welcome.

@supermaxiste, @cmdoret : Can we push this repo into a working mode where we try to apply as many Best Practices as possible.
We are already doing nice, PRs have all a convention commit title.
Commits are conventional commits. When we merge, the commits on the branch should follow conv. commit message format, otherwise squash merge and make one proper description (I always do that).
So we can just take this repository as a test piece with the team to see how far can we push it.
So CI will come. I would like to add one either on Github
(prefer Gitlab because Github CI is akward with their actions setup, even unsecure too... I can give it a try, might be good too to not have predjustice, but among DevOps Github it does not have a good reputation)

@cmdoret
Copy link
Member

cmdoret commented Jun 19, 2024

Cool, yeah the PR template looks good to me; short and to the point. I like the idea of having a checklist in there :)

@cmdoret
Copy link
Member

cmdoret commented Jun 19, 2024

I think we gotta stay on Github (at least for now), but for actions related to conventional commits, @supermaxiste already set something up in other repos, we could maybe reuse it here :)

@gabyx
Copy link
Contributor Author

gabyx commented Jun 19, 2024

I mean, Gitlab can run CI and report to Github, cant it? I mean we just need to push to both urls. Ok the branch do not get deleted when PRs close etc... but jeah...

Github Actions why they are bad: https://www.youtube.com/watch?v=9qljpi5jiMQ
This is a really really profound review why they are really not so ideal. also the author is actually a really good rust streamer lol

@cmdoret
Copy link
Member

cmdoret commented Jun 20, 2024

Thanks for the link @gabyx, I understand what you mean now.
I am personally not against connecting a gitlab CI/CD project to this repo, we can discuss it with the team.

@gabyx gabyx force-pushed the feat/add-pr-template branch from 61f3a07 to 952593b Compare June 20, 2024 09:53
@gabyx gabyx force-pushed the feat/add-pr-template branch from 952593b to 5dc644b Compare June 20, 2024 09:54
@cmdoret cmdoret self-requested a review June 20, 2024 10:04
@cmdoret cmdoret added the documentation Improvements or additions to documentation label Jun 20, 2024
@gabyx gabyx merged commit be3551b into main Jun 20, 2024
@gabyx gabyx deleted the feat/add-pr-template branch June 20, 2024 19:31
supermaxiste pushed a commit that referenced this pull request Jun 24, 2024
supermaxiste pushed a commit that referenced this pull request Jun 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants