Commit 69150f5e authored by Yoginth's avatar Yoginth 🍪

1.0.1

parent f9a50b15
Pipeline #59605149 passed with stages
in 2 minutes and 57 seconds
## :eight_spoked_asterisk: :stars: :sparkles: :dizzy: :star2: :sparkles: :dizzy: :star2: :star2: Contributing :star: :star2: :dizzy: :sparkles: :star: :dizzy: :sparkles: :stars: :eight_spoked_asterisk:
So, you want to contribute to this project! That's awesome. However, before
doing so, please read the following simple steps how to contribute. This will
make the life easier and will avoid wasting time on things which are not
requested. :sparkles:
## Discuss the changes before doing them
- First of all, open an issue in the repository, using the bug tracker,
describing the contribution you would like to make, the bug you found or any
other ideas you have. This will help us to get you started on the right
foot.
- If it makes sense, add the platform and software information (e.g. operating
system, Python version etc.), screenshots (so we can see what you are
seeing).
- It is recommended to wait for feedback before continuing to next steps.
However, if the issue is clear (e.g. a typo) and the fix is simple, you can
continue and fix it.
## Fixing issues
- Fork the project in your account and create a branch with your fix:
`some-great-feature` or `some-issue-fix`.
- Commit your changes in that branch, writing the code following the
code style. If the project contains tests (generally, the `test`
directory), you are encouraged to add a test as well. :memo:
## Creating a pull request
- Open a pull request, and reference the initial issue in the pull request
message (e.g. *fixes #<your-issue-number>*). Write a good description and
title, so everybody will know what is fixed/improved.
- If it makes sense, add screenshots, gifs etc., so it is easier to see what
is going on.
## Wait for feedback
Before accepting your contributions, we will review them. You may get feedback
about what should be fixed in your modified code. If so, just keep committing
in your branch and the pull request will be updated automatically.
## Everyone is happy!
Finally, your contributions will be merged, and everyone will be happy! :smile:
Contributions are more than welcome!
Thanks! :sweat_smile:
MIT License
Copyright (c) 2018 Yoginth
Copyright (c) 2019 Yoginth
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
......
......@@ -54,24 +54,8 @@ Specify an object with any of the following properties:
- [Sindresorhus's to-milliseconds](https://github.com/sindresorhus/to-milliseconds)
## Get Help
There are few ways to get help:
1. Please [post questions on Stack Overflow](https://stackoverflow.com/questions/ask). You can open issues with questions, as long you add a link to your Stack Overflow question.
2. For bug reports and feature requests, open issues.
3. For direct and quick help, you can [email me](mailto://yoginth@zoho.com).
## How to contribute
Have an idea? Found a bug? See [how to contribute][contributing].
Thanks!
## License
[MIT][license]
[MIT][license] Yoginth
[LICENSE]: https://yoginth.mit-license.org/
[contributing]: /CONTRIBUTING.md
[LICENSE]: https://mit.yoginth.com
......@@ -8,11 +8,11 @@ setuptools.setup(
packages = ["tomilliseconds"],
long_description = long_description,
long_description_content_type = "text/markdown",
version = "1.0.0",
version = "1.0.1",
description = "Convert an object of time properties to milliseconds: {'seconds': 10} → 10000",
author = "Yoginth",
author_email = "yoginth@zoho.com",
url = "https://yoginth.gitlab.io",
author_email = "me@yoginth.com",
url = "https://yoginth.com",
classifiers=(
"Programming Language :: Python",
"Natural Language :: English",
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment