Skip to content

Commit

Permalink
Changing Redis references in files documenting development guidelines (
Browse files Browse the repository at this point in the history
…#26) (#45)

Changing some references from
Redis to placeholderkv.

Signed-off-by: Parth Patel <661497+parthpatel@users.noreply.github.com>
  • Loading branch information
parthpatel authored Mar 27, 2024
1 parent 3782446 commit 11ddd8b
Show file tree
Hide file tree
Showing 2 changed files with 4 additions and 4 deletions.
2 changes: 1 addition & 1 deletion BUGS
Original file line number Diff line number Diff line change
@@ -1 +1 @@
Please check https://github.com/redis/redis/issues
Please check https://github.com/placeholderkv/placeholderkv/issues
6 changes: 3 additions & 3 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -19,9 +19,9 @@ There is also an active community of Redis users at Stack Overflow:

https://stackoverflow.com/questions/tagged/redis

Issues and pull requests for documentation belong on the redis-doc repo:
Issues and pull requests for documentation belong on the placeholderkv-doc repo:

https://github.com/redis/redis-doc
https://github.com/placeholderkv/placeholderkv-doc

If you are reporting a security bug or vulnerability, see SECURITY.md.

Expand All @@ -37,7 +37,7 @@ Here you can see if there is consensus about your idea.
2. If in step 1 you get an acknowledgment from the project leaders, use the
following procedure to submit a patch:

a. Fork Redis on GitHub ( https://docs.github.com/en/github/getting-started-with-github/fork-a-repo )
a. Fork placeholderkv on GitHub ( https://docs.github.com/en/github/getting-started-with-github/fork-a-repo )
b. Create a topic branch (git checkout -b my_branch)
c. Push to your branch (git push origin my_branch)
d. Initiate a pull request on GitHub ( https://docs.github.com/en/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request )
Expand Down

0 comments on commit 11ddd8b

Please sign in to comment.