Skip to content

Commit

Permalink
Feat: Update old information and resolve some typos
Browse files Browse the repository at this point in the history
  • Loading branch information
Anuj-Rathore24 committed Jul 19, 2024
1 parent 553450b commit 8649e42
Showing 1 changed file with 6 additions and 6 deletions.
12 changes: 6 additions & 6 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ Replace WordPress default search with Google Custom Search results.

**Requires at least:** 4.8

**Tested up to:** 6.4.2
**Tested up to:** 6.6

**License:** [GPLv2 or later](http://www.gnu.org/licenses/gpl-2.0.html)

Expand Down Expand Up @@ -39,23 +39,23 @@ This plugin will replace the WordPress default search query with server-side res

Before creating a new issue, do browse through the [existing issues](https://github.com/rtCamp/search-with-google/issues) for resolution or upcoming fixes.

If you still need to [log an issue](https://github.com/rtCamp/search-with-google/issues/new), making sure to include as much detail as you can, including clear steps to reproduce your issue if possible.
If you still need to [log an issue](https://github.com/rtCamp/search-with-google/issues/new), make sure to include as much detail as you can, including clear steps to reproduce your issue, if possible.

### Creating a pull request

Want to contribute a new feature? Start a conversation by logging an [issue](https://github.com/rtCamp/search-with-google/issues).
Want to contribute to add a new feature? Start a conversation by creating an [issue](https://github.com/rtCamp/search-with-google/issues).

Once you're ready to send a pull request, please run through the following checklist:
Once you're ready to create pull request, please go through the following checklist:

1. Browse through the [existing issues](https://github.com/rtCamp/search-with-google/issues) for anything related to what you want to work on. If you don't find any related issues, open a new one.

1. Fork this repository.

1. Create a branch from `develop` for each issue you'd like to address and commit your changes.

1. Push the code changes from your local clone to your fork.
1. Push the changes in the code, from your local clone to your fork.

1. Open a pull request and that's it! We'll with feedback as soon as possible (Isn't collaboration a great thing? 😌)
1. Open a pull request and that's it! We'll reach back with feedback as soon as possible (Isn't collaboration a great thing? 😌)

1. Once your pull request has passed final code review and tests, it will be merged into `develop` and be in the pipeline for the next release. Props to you! 🎉

Expand Down

0 comments on commit 8649e42

Please sign in to comment.