You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+53Lines changed: 53 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,6 +6,27 @@ Generate random, human-friendly names, like `determined-pancake` or `sinister di
6
6
7
7
fname isn't meant to provide a secure, globally unique identifier, but with over 500 billion possible combinations, it's good enough for most non-critical use cases.
Note: the minimum phrase size is 2 (default), and the maximum is 4.
67
88
89
+
Generate a name phrase with a specific casing:
90
+
91
+
```sh
92
+
$ fname --casing upper
93
+
TRAGIC-MOUNTAIN
94
+
95
+
$ fname --casing title
96
+
Whimsical-Party
97
+
```
98
+
68
99
Specify the seed for generating names:
69
100
70
101
```sh
@@ -129,6 +160,28 @@ fname is not cryptographically secure, and should not be used for anything that
129
160
130
161
fname's dictionary is curated to exclude words that are offensive, or could be considered offensive, either alone or when generated in a phrase. Nevertheless, all cases are not and cannot be covered. If you find a word that you think should be removed, please [open an issue](https://github.com/Splode/fname/issues).
131
162
163
+
## Contributing
164
+
165
+
We welcome contributions to the fname project! Whether it's reporting bugs, suggesting improvements, or submitting new features, your input is valuable to us. Here's how you can get started:
166
+
167
+
1. Fork the repository on GitHub.
168
+
2. Clone your fork and create a new branch for your changes.
169
+
3. Make your changes and commit them to your branch.
170
+
4. Create a pull request, and provide a clear description of your changes.
171
+
172
+
Before submitting a pull request, please make sure your changes are well-tested and adhere to the code style used throughout the project. If you are unsure how to proceed or need help, feel free to open an issue or ask a question in the [discussions](https://github.com/Splode/fname/discussions) section.
173
+
174
+
### Reporting Issues
175
+
176
+
If you encounter a bug or any issue, please [open an issue](https://github.com/Splode/fname/issues) on GitHub. When reporting a bug, try to include as much information as possible, such as the steps to reproduce the issue, the expected behavior, and the actual behavior. This will help us diagnose and fix the issue more efficiently.
177
+
178
+
### Suggesting Improvements
179
+
180
+
We are always looking for ways to improve fname. If you have a suggestion for a new feature or an enhancement to an existing feature, please [open an issue](https://github.com/Splode/fname/issues) or start a discussion in the [discussions](https://github.com/Splode/fname/discussions) section. Be sure to explain your idea in detail, and if possible, provide examples or use cases.
181
+
182
+
Thank you for your interest in contributing to fname!
0 commit comments