-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
[Fixes - Documentation] update the CONTRIBUTING.md with Issues & Pull Requests sections #4934
[Fixes - Documentation] update the CONTRIBUTING.md with Issues & Pull Requests sections #4934
Conversation
Open discussion: Suggestions regarding the content added are welcome, please review and see if the outline provided for Issues & Pull Requests as well as Reviewing Pull Requests are in line with the organization's expectations. If this template is agreed upon then I will move forward with adding it to the remaining repos. |
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.
Thanks @sandramsc for your time and contribution. I have some suggestions.
I would not recommend putting negative words like "rude, disrespectful or aggressive" on the contribution page. The content should be positive, friendly and appealing to the newcomers.
Can you please check the lowercase and uppercase of some words like "issue, pull request" also make first letter capital on each sentence after colon ":" ?
There is also a need of rephrasing content.
@Chadha93 and @leecalcote please confirm if we need png format of the images in integrations directory .
Thanks for your feedback @goldfishdolphin . It's interesting to see your perspective on these words and the context a reader (contributor) might perceive them to be. From my perspective in this context, I see them as words describing a particular type of behaviour or tone (when it comes to writing). I left these words in the template to echo the text in the existing Code of Conduct section of the CONTRIBUTING.md . "Instances of abusive, harassing, or otherwise unacceptable behaviour may be reported by contacting [email protected]." I can sum the mentioned words up as "unacceptable behaviour" as is in the quote above? |
@sandramsc are all these commits related to updating contributing.md file? |
@goldfishdolphin they arn't, I wasn't sure why they were pushed to this branch as I created, checked out, worked and pushed each task to its respective branch i.e (sandramsc:contributing/sandramsc/4932.. and sandramsc:screenshots/...), alas when I pushed to make a PR for this issue...the non-related commits from the later branch are showed here too. Working on a fix to remove unrelated changes and study the initial cause. Update: even with the most recent push having, newly forked the repo, newly created the contributing/sandramsc/4932 to work on the CONTRIBUTING.md file, commits from another branch I'm currently making changes to have been pushed here. Perhaps deleting the other branch first, then making a push to this branch will resolve the issue - will try that when updating the docs after receiving feedback from all reviewers. |
let's discuss this item on today's website meeting, |
…its in the contributing/sandramsc/4932 branch Signed-off-by: Sandra Ashipala <[email protected]>
🚀 Preview for commit fc911fc at: https://6511f686cdf0b61326f97bdd--layer5.netlify.app |
ok @sandramsc i understood, why you are facing this, see the thing is if you are creating a new branch not going to master branch first before creating than in that caase you will get the changes reflected in pr of that branch too from where you have created a new branch, in your case this thing is happening. |
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.
I think this is very well put together. In absence of any major omissions, it think this should be merged. Well done @sandramsc
In context of "Pull Request Etiquette", alternatively, we might offer this sentiment's corollary, which could be: "exercise patience and empathy while offering critiques of the works of others." |
🚀 Preview for commit 9b41463 at: https://6542b2fb6e1b3825f1450cd0--layer5.netlify.app |
🚀 Preview for commit 155a1c4 at: https://6543df20aa65292ed991b619--layer5.netlify.app |
@leecalcote Thanks for the feedback, moving forward with the suggested changes and converting this draft PR into an open one. |
…ramsc/layer5 into contributing/sandramsc/4932
…rased wordings of sentences in CONTRIBUTING.md section ##Issues & Pull Requests, based on initial feedback Signed-off-by: Sandra Ashipala <[email protected]>
🚀 Preview for commit 1e0f7b1 at: https://65451ad4895d1100689fdb0b--layer5.netlify.app |
🚀 Preview for commit c819d45 at: https://656d8d15745efd299973b887--layer5.netlify.app |
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.
Yay!
Finally, someone clicked the merge button!😅
Signed-off-by: Lee Calcote <[email protected]>
I made a couple of modifications, the majority of which retained the original intent with only one or two augmenting the intent. You exercised no small amount of patience on this, @sandramsc. Kudos to you for hangin' tough and seeing this through. |
Description
This PR fixes #4932
Notes for Reviewers
There are 9 repositories connected to this issue where the same template added to the CONTRIBUTING.md of this layer5 repo will be added. This PR should only be considered for closure once all projects on the checklist have been updated (I will indicate this with a comment).
Signed commits