Skip to content

Conversation

@Chaitanyassr
Copy link

fix issue #341

@akshatkarani
Copy link
Member

Change your commit message to follow commit guidelines. Also never open a PR from your master branch.

@Chaitanyassr
Copy link
Author

Change your commit message to follow commit guidelines. Also never open a PR from your master branch.

done, changed the message . for the branch part..i will keep this in mind in future .
or do you want me to open a different pr with a different branch for this one?

Copy link
Member

@utkarsh2102 utkarsh2102 left a comment

Choose a reason for hiding this comment

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

Hey,

If you're still interested, just some trivial things:
-> add the issue being fixed in the commit messages.
-> rebase this PR, please.
-> [optional] in case you're interested, you can create a different branch and then change the base easily. You don't need a separate PR for sure!

@sonarqubecloud
Copy link

Kudos, SonarCloud Quality Gate passed!

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
No Duplication information No Duplication information

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

Labels

None yet

Development

Successfully merging this pull request may close these issues.

3 participants