Skip to content

docs: fix typo in README#1654

Merged
lbergelson merged 1 commit intosamtools:masterfrom
Manice18:master
Feb 17, 2023
Merged

docs: fix typo in README#1654
lbergelson merged 1 commit intosamtools:masterfrom
Manice18:master

Conversation

@Manice18
Copy link
Contributor

@Manice18 Manice18 commented Feb 17, 2023 •
edited
Loading

Corrected multiple spelling errors in the README

Description

Please explain the changes you made here.
Explain the motivation for making this change. What existing problem does the pull request solve?

Things to think about before submitting:

  • Make sure your changes compile and new tests pass locally.
  • Add new tests or update existing ones:
    • A bug fix should include a test that previously would have failed and passes now.
    • New features should come with new tests that exercise and validate the new functionality.
  • Extended the README / documentation, if necessary
  • Check your code style.
  • Write a clear commit title and message
    • The commit message should describe what changed and is targeted at htsjdk developers
    • Breaking changes should be mentioned in the commit message.

@Manice18
docs: fix typo in README
c454b12 
Corrected multiple spelling errors in the README
lbergelson
lbergelson approved these changes Feb 17, 2023
View reviewed changes
Copy link
Member

@lbergelson lbergelson left a comment

Choose a reason for hiding this comment

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

@Manice18 Thank you!

@lbergelson lbergelson merged commit b0a5165 into samtools:master Feb 17, 2023
@Manice18
Copy link
Contributor Author

Manice18 commented Feb 17, 2023

@lbergelson i had a small query which is whether your organization will be a part of gsoc this year or not?

@lbergelson
Copy link
Member

lbergelson commented Feb 17, 2023

Is that google summer of code? I don't know of any plans to be part of that. I don't know how that is set up or run. If google wants to pay people to work on htsjdk I think we'd be happy to have their help though :)

@Manice18
Copy link
Contributor Author

Manice18 commented Feb 17, 2023

thanks for the info @lbergelson
If your org is taking part then I would be willing to pick your org, if then please guide me through it .

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

Reviewers

@lbergelson lbergelson lbergelson approved these changes

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@Manice18 @lbergelson