Skip to content

Commit 4b7db3e

Browse files
authored
Merge pull request #5 from leozz37/feature-refactor-docs
Feature refactor docs
2 parents 5597cb5 + 2473762 commit 4b7db3e

File tree

1 file changed

+7
-72
lines changed

1 file changed

+7
-72
lines changed

README.md

Lines changed: 7 additions & 72 deletions
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ Hare is a user-friendly lib for sockets in Golang. You can send and listen to TC
2525
- [Contributing](#contributing)
2626
- [License](#license)
2727

28-
## Installation
28+
## 🖥️ Installation
2929

3030
First, you need [Go](https://golang.org/) installed (version 1.12+ is required), then you can install Hare:
3131

@@ -47,7 +47,7 @@ $ brew tap leozz37/jaguar
4747
$ brew install jaguar
4848
```
4949

50-
## Quickstart
50+
## 🍕 Quickstart
5151

5252
[Sample code](./examples/send.go) for sending payloads:
5353

@@ -85,7 +85,7 @@ func main() {
8585
}
8686
```
8787

88-
## Documentation
88+
## 📖 Documentation
8989

9090
The library consists of two features: **listen** and **send** to a given port. You can check the full documentation on [Godoc](https://pkg.go.dev/github.com/leozz37/hare#section-documentation).
9191

@@ -195,7 +195,7 @@ func main() {
195195
}
196196
```
197197
198-
## Examples
198+
## 📙 Examples
199199
200200
You can check the [example](./examples) for code usages, like [send](./examples/send.go) and [listen](./examples/listen.go) samples.
201201
@@ -233,7 +233,7 @@ func main() {
233233
}
234234
```
235235
236-
## Testing
236+
## 🧪 Testing
237237
238238
To run the test suite, you can run with:
239239
@@ -247,75 +247,10 @@ If you want a more detailed report with coverage and an `coverage.out` file, do
247247
$ go test -v -covermode=count -coverprofile=coverage.out
248248
```
249249
250-
## Contributing
250+
## 🤝 Contributing
251251
252252
A full guideline about contributing to Hare can be found in the [CONTRIBUTING.md](./CONTRIBUTING.md) file.
253253
254-
### Issues
255-
256-
Use the search tool before opening a new issue.
257-
258-
Please provide source code and commit sha if you found a bug.
259-
260-
Review existing issues and provide feedback or react to them.
261-
262-
### Pull requests
263-
264-
Open your pull request against ```develop```.
265-
266-
You should add/modify tests to cover your proposed code changes.
267-
268-
Test coverage should never go down from 90%.
269-
270-
If your pull request contains a new feature, please document it on the README.
271-
272-
### Branching
273-
274-
The ```main``` is a **regular branch** which always contains the latest
275-
**stable** codebase and must **never** be broken.
276-
277-
The ```develop``` is a **regular branch** which always contains the latest
278-
**development** codebase and **eventually** can be broken. But you'll need to
279-
accept the **sombrero of shame** if you do that.
280-
281-
The ```experimental``` is a **temporary branch** which contains a new feature or
282-
idea. You must use the following name convention: **experimental-brief-description**.
283-
284-
The ```feature``` is a **temporary branch** which contains a new feature under
285-
development that later will be merged against the development branch. You must
286-
use the following name convention: **feature-brief-description**.
287-
288-
The ```bugfix``` is a **temporary branch** which contains the necessary fix to be
289-
applied **after** a specific release to be merged against the development branch.
290-
You must use the following name convention: **bugfix-brief-description**.
291-
292-
The ```hotfix``` is a **temporary branch** which contains a critical fix to be
293-
applied **immediately** and merged against the main and the development branches.
294-
You must use the following name convention: **hotfix-brief-description**.
295-
296-
Feel free to apply the labels from GitHub to the branches, they are very helpful.
297-
298-
### Versioning
299-
300-
The project uses the [semantic versioning 2.0.0](https://semver.org) in
301-
order to control the version numbers.
302-
303-
### Commiting
304-
305-
The ```main```, ```develop``` and ```release``` branches have protection rules
306-
against **push**.
307-
308-
To contribute you must create a new branch following the [branching](#branching)
309-
guideline and once your work is done, open a **pull request** from your branch
310-
to the **develop** branch.
311-
312-
The **pull request** will trigger the test suites automatically
313-
and the code must **pass all the tests** and also be reviewed and approved
314-
before merged in the **develop** branch (or even ``main`` or ``release`` in case
315-
of a ``*fix``).
316-
317-
Feel free to apply the labels from GitHub to the pull requests, they are very helpful.
318-
319-
## License
254+
## ⚖️ License
320255
321256
Hare is released under the [MIT License](./LICENSE).

0 commit comments

Comments
 (0)