CONTRIBUTING.md

Contributing Guidelines

With pleasure happy to invite you to collaborate on developing this repository! 💕

👉 Note: before participating in our community, please read our Code Of Conduct. By interacting with this repository, organization, or community you agree to abide by its terms.

👑 Community Guidelines

Hi there! We're thrilled that you'd like to contribute to this project. Your help is essential for keeping it great.

Please review our Code Of Conduct. It is in effect at all times. We expect it to be honored by everyone who contributes to this project. Acting like an asshole will not be tolerated.

In this guide you will get an overview of the contribution workflow from opening an issue, creating a PR, reviewing, and merging the PR.

There’s several ways to contribute, not just by writing code. If you have questions, see Support file.

👀 Finding Good, Filing Bugs and Change Requests

Before spending lots of time on something, ask for feedback on your idea first!

Please search issues and pull requests before adding something new to avoid duplicating efforts and conversations.

This project welcomes non-code contributions, too! The following types of contributions are welcome:

• Ideas: participate in an issue thread or start your own to have your voice heard.
• Writing: contribute your expertise in an area by helping expand the included docs.
• Copy editing: fix typos, clarify language, and improve the quality of the docs.
• Formatting: help keep docs easy to read with consistent formatting.

💡 Asking Any Questions Support

See our Support Guide. In short, GitHub issues are not the appropriate place to debug your specific project, but should be reserved for filing bugs and feature requests.

📥 Bug Reports and Other Issues

If you find any problems in the coding provided by StephanusDai. You can submit a new Trouble Tickets reposity.

💡 Forum Discussions

Communicate well to find what you are looking for through this Discussions reposity.

⚠️ WARNING!
The Issue Forms and Discussion Forums in each repository are different from Global Discussions and Global Issues, therefore it is highly recommended if you want to provide suggestions and send bug report that are very valuable to me.

🍷 Request for Changes / Pull Requests

You first need to create a fork of the ShellLinuxAutoBackupFile repository to commit your changes to it. Methods to fork a repository can be found in the GitHub Documentation.

Then add your fork as a local project:

# Using HTTPS
git clone https://github.com/wiefunkdai/ShellLinuxAutoBackupFile.git

# Using SSH
git clone git@github.com:wiefunkdai/ShellLinuxAutoBackupFile.git

Which remote URL should be used ?

Then, go to your local folder

cd ShellLinuxAutoBackupFile

Add git remote controls :

# Using HTTPS
git remote add fork https://github.com/YOUR-USERNAME/ShellLinuxAutoBackupFile.git
git remote add upstream https://github.com/wiefunkdai/ShellLinuxAutoBackupFile.git


# Using SSH
git remote add fork git@github.com:YOUR-USERNAME/ShellLinuxAutoBackupFile.git
git remote add upstream git@github.com/wiefunkdai/ShellLinuxAutoBackupFile.git

You can now verify that you have your two git remotes:

git remote -v

Receive remote updates

In view of staying up to date with the central repository :

git pull upstream master

Choose a base branch

Before starting development, you need to know which branch to base your modifications/additions on. When in doubt, use master.

Type of change		Branches
Documentation		master
Bug fixes		master
New features		master
New issues models		YOUR-USERNAME:patch

# Switch to the desired branch
git switch master

# Pull down any upstream changes
git pull

# Create a new branch to work on
git switch --create patch/1234-name-issue

Commit your changes, then push the branch to your fork with git push -u fork and open a pull request on the ShellLinuxAutoBackupFile repository following the template provided.

📝 Contrib with Under License

Any contributions you make will be under the BSD Software License

In short, when you submit changes, your submissions are understood to be under the same BSD-3 Clause License that covers the project. Feel free to contact the maintainers if that's a concern.

License of All Free Open Sources

By contributing, you agree that your contributions will be licensed under its BSD-3 Clause License.

License of Official and User-contributed Documentation

The text contained in the official and user-contributed project documentation as stated as other content on project, except the license projects or documents themselves and as otherwise noted, is licensed under the Creative Commons Attribution 4.0 International (CC-BY-4.0).

See [Support][support] for details.

🌹 Funds or Financial support

I open-source almost everything I can and try to reply to everyone needing help using these projects. Obviously, this takes time. You can use this service for free.

If you are using this project and are happy with it or just want to encourage me to continue creating stuff, there are a few ways you can do it:

• Giving proper credit on the GitHub Sponsors page.
• Starring and sharing the project ⭐
• You can make one-time donations via PayPal. I'll probably buy a coffee ☕ or tea 🍵 or cake 🍰
  
• It’s also possible to support mine financially by becoming a backer or sponsor through
  

However, I am available for hire. You can also give me career opportunities to help your business in developing the software you need. Please contact me at:

🙏 Thanks for your contribute and support! 😍 ❤️

Any Questions & Other Supports? see Support please.

---

Visit Website · Global Issues · Global Discussions · Global Wiki

Copyright © ID 2023 Stephanus Bagus Saputra (www.stephanusdai.web.id)
All rights reserved.