Skip to content

Update STYLE.md #574

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

Open
wants to merge 1 commit into
base: blog-functional
Choose a base branch
from

Conversation

Gurnoor-coding
Copy link

@Gurnoor-coding Gurnoor-coding commented Jun 19, 2025

Keploy API Fellowship, I am a person who is new, so I decided to just test the pull request feature. I have done so by adding to the README, I have added a purpose statement, and some more hopefully helpful information.

What has changed?

Added further examples and helpful information.

This PR Resolves #(API Fellowship Session 1)

Type of change

Please delete options that are not relevant.

  • Documentation update (if none of the other choices apply).

How Has This Been Tested?

Please run npm run build and npm run serve to check if the changes are working as expected. Please include screenshots of the output of both the commands. Add screenshots/gif of the changes if possible.

Checklist:

  • My code follows the style guidelines of this project.
  • I have performed a self-review of my own code.

Keploy API  Fellowship, I am a person who is new, so I decided to just test the pull request feature. I have done so by adding to the README, I have added a purpose statement, and some more hopefully helpful information.

Signed-off-by: Gurnoor-coding <[email protected]>
Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

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

Thank you and congratulations 🎉 for opening your very first pull request in keploy

Copy link

@pratik-mahalle pratik-mahalle left a comment

Choose a reason for hiding this comment

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

Hey @Gurnoor-coding, Thanks for raising this pr.
Unfortunately, this PR doesn’t include any meaningful changes. You can do so on the specific two repositories that we provided. In the future, please ensure that a PR in this repo is raised only if you’ve made substantial updates or solved a particular issue. This helps keep the process efficient and organized.
This being a part of an assignment in api fellowship would be counted since you were supposed to create a pr but wont be merged since this is not that relevant of a change. I’m sure you understand, and I appreciate your cooperation on this. We will be closing this PR for now.

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.

2 participants