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

Fixed Typos in intro.md and CONTRIBUTING.md #1735

Closed
wants to merge 3 commits into from
Closed

Fixed Typos in intro.md and CONTRIBUTING.md #1735

wants to merge 3 commits into from

Conversation

mdxabu
Copy link
Contributor

@mdxabu mdxabu commented Dec 14, 2023

Dear Maintainer,

I wanted to inform you that I have made some typos and grammar corrections in the CONTRIBUTING.md and intro.md file. I have opened a PR for the changes to be reviewed and merged.

Best regards,
F Mohamed Abdullah

CONTRIBUTING.md Outdated
@@ -68,7 +68,7 @@ with your real name (first and last name)
If you set your `user.name` and `user.email` git configs, you can sign your
commit automatically with `git commit -s`. If you forgot this you can
use `git commit -s --amend` to add this in retrospective for the last commit.
If you need to sign-off multiple commits within a branch, you need to do an interactive
If you need to sign off multiple commits within a branch, you need to do an interactive
Copy link
Member

Choose a reason for hiding this comment

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

Please keep sign-off . It implies user to use git commit --sign-off

Copy link
Contributor Author

Choose a reason for hiding this comment

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

ok

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I changed that @rohanKanojia

@mdxabu mdxabu requested a review from rohanKanojia December 14, 2023 10:21
CONTRIBUTING.md Outdated
@@ -34,22 +34,22 @@ license document, but changing it is not allowed.

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:
By contributing to this project, I certify that:
Copy link
Member

Choose a reason for hiding this comment

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

I think this is directly taken from https://developercertificate.org/

I would not modify text in this code block. It should exactly match it's source.

Copy link
Contributor Author

@mdxabu mdxabu Dec 15, 2023

Choose a reason for hiding this comment

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

@rohanKanojia , I've just changed that phrase to https://developercertificate.org/

@rohanKanojia
Copy link
Member

@mdxabu Could you please squash your commits into one?

@mdxabu
Copy link
Contributor Author

mdxabu commented Dec 15, 2023

@mdxabu Could you please squash your commits into one?

@rohanKanojia , I Squashed those commits into one commit.

@mdxabu mdxabu requested a review from rohanKanojia December 15, 2023 06:12
@rohanKanojia
Copy link
Member

@mdxabu : Thanks, could you please address #1735 (comment) as well?

@mdxabu
Copy link
Contributor Author

mdxabu commented Dec 15, 2023

@mdxabu : Thanks, could you please address #1735 (comment) as well?

Ok

CONTRIBUTING.md Outdated
permitted to submit under a different license), as indicated
in the file; or

(c) The contribution was provided directly to me by some other
person who certified (a), (b) or (c) and I have not modified
the person who certified (a), (b) or (c) and I have not modified
Copy link
Collaborator

Choose a reason for hiding this comment

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

This needs to be corrected. And please, as @rohanKanojia mentioned, don't touch the Developer's Certificate of Origin part as we do not own this; we just replicate it here. If you want to update this, please get in touch with the Linux Foundation, when they change it, we will take it over here. Consider it like a law text, you can't change it even with errors.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

This needs to be corrected. And please, as @rohanKanojia mentioned, don't touch the Developer's Certificate of Origin part as we do not own this; we just replicate it here. If you want to update this, please get in touch with the Linux Foundation, when they change it, we will take it over here. Consider it like a law text, you can't change it even with errors.

I deleted that commit that I changed that Developer's Certificate. Now I just made changes only in into.md and CONTRIBUTING.md

@rhuss
Copy link
Collaborator

rhuss commented Dec 20, 2023

@mdxabu thanks for the PR! Looks good to me, but please leave the part untouched that we copy over from somewhere. See my inline comment.

Copy link

codecov bot commented Dec 20, 2023

Codecov Report

Merging #1735 (bd85000) into master (88fb191) will increase coverage by 0.08%.
Report is 6 commits behind head on master.
The diff coverage is n/a.

Additional details and impacted files
@@             Coverage Diff              @@
##             master    #1735      +/-   ##
============================================
+ Coverage     65.23%   65.31%   +0.08%     
- Complexity     2274     2280       +6     
============================================
  Files           172      172              
  Lines         10173    10184      +11     
  Branches       1403     1406       +3     
============================================
+ Hits           6636     6652      +16     
+ Misses         2984     2983       -1     
+ Partials        553      549       -4     

see 8 files with indirect coverage changes

@mdxabu
Copy link
Contributor Author

mdxabu commented Dec 20, 2023

@mdxabu thanks for the PR! Looks good to me, but please leave the part untouched that we copy over from somewhere. See my inline comment.

I Changed that please go through it, if you have any questions please ping me here, Does this repo have any discussion channel?

@mdxabu mdxabu requested a review from rhuss December 20, 2023 07:55
@mdxabu mdxabu closed this Dec 20, 2023
@mdxabu mdxabu reopened this Dec 20, 2023
Copy link

Quality Gate Passed Quality Gate passed

Kudos, no new issues were introduced!

0 New issues
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarCloud

@mdxabu mdxabu closed this by deleting the head repository Dec 20, 2023
@rhuss
Copy link
Collaborator

rhuss commented Dec 20, 2023

Thanks, looks good now! But it looks also like you closed the PR or deleted the original repository.

wrt/ Discussions: Sorry, we don't have yet but that is probably a good idea to enable GitHub discussions. Wdyt, @rohanKanojia ?

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

Successfully merging this pull request may close these issues.

3 participants