-
-
Notifications
You must be signed in to change notification settings - Fork 9
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
Implement GitHub PR Issue Checker Workflow #28
Comments
I will assign you the issuue, once i am thorough with your understanding. Please answer all 4 qusetions. |
I mean for addition of a workflow...which literally won't do any changes to my project, people are asking(or rather expecting) for a Level 3 tag. I would have liked to say any major changes, but in this case it isn't doing any change at all. |
I have contributed to other projects on this issues!! Refrence:- Research-Nexas/Research-Nexas#275 One of the PA gave level3 and one gave level3! |
I'm expecting level2 or a level3!! |
Ok that was more than 4 lines!! I was expecting 4 answers. Also i am going to ask about this in our PA channel in discord about this and thanks for highlighting those projects. I would take them as reference. |
Also one more question, answer with yes or no. |
No. |
.. Thanks for the response. |
Yes. Wait I'm joining the channel!! |
Can I get the discord link?? |
Actually i was asking about these qusetions. I asked 4 and you replied to only 1 of them. Do answer all!! Also i am having a conversation about this in the project admins channel with the Program Manager. And contributors(including you) are not allowed to view the PA channel. Once confirmed it is a level 3 tag, i will give you the level3 tag. But if the program manager says it is a level 1, then i am afraid your other 2 contributions listed here, might as well get converted to a level 1 tag(if you have only done this change and nothing else). But sure, you can have the discord link: https://discord.com/invite/nxBmE5z9Eh |
Okay I can do it for any level!!! |
The end that matters is just contributions!! Not points!! @prrockzed |
Sure, i totally agree. Rest assured, i will assign you the issue as you are so keen on contributing. |
I have given the labels. But i will assign you the issue, once you answer the question: Have you written this issue yourself? |
Yaa. I have written this issues my self! And I copy paste the same issue with in other repos!! Some repos gave level3 some gave level2! It' s a strategic move!! Just make a issue on a topic and implement it on every repo! You can get assigned to half of the issue!! 😁 |
Hi @smog-root, I’ve already informed you not to raise more workflow issues, and what I said above is applies only to unique contributors. You already have 30+ merged PRs for workflows alone, which is excessive. Have you participated in GSSoC only for workflows? You need to contribute something more impactful for the website or projects, not just for repository workflows. Also, you mentioned, "I copy-paste the same issue in other repos! Some repos gave level 3, some gave level 2! It’s a strategic move!" While it may be a strategic move, it only looks good when done less. Workflow improvements are for repository actions, not for website development. your contributions should focus more on the website developments |
Okay I got you point!! I have done some website development too! I'm work on it too! I will make sure to do more impactful PR form now on!! Just saying: I was just expecting to get level3 or level2 for 4 workflows. As you said for workflows. I can get only 2 or 1. I will remember it!! |
R u working on the issue? |
No. I will close it!! Now. I stopped working on workflows.. as mod suggested me!! @MastanSayyad |
Description: We need to create a GitHub Actions workflow that automates the validation of pull requests (PRs). This workflow will ensure that all PRs meet the following criteria before being merged:
PR Description Check: Every PR must have a description. If the description is missing, the PR should fail the check.
Issue Reference Check: The PR description must include an issue reference in the format Fixes #. If the PR is not addressing an existing issue, it should mention Fixes #NEW as a placeholder.
Acceptance Criteria:
The workflow checks the PR body for:
If the criteria are not met:
If the checks pass:
Expected Output:
Additional Notes:
Note: i'm expecting a gssoc-ext with level3 (or) level2 and a hacktoberfest-accepted label!
@prrockzed
The text was updated successfully, but these errors were encountered: