Can I Dare You? Contribute to the fck. Framework!

Greetings, brave souls (or whatever), who have stumbled upon the fck framework! If you find yourself strangely drawn to contributing to this project, we begrudgingly acknowledge your presence and, reluctantly, invite you to join the ranks of contributors. But before you dive headfirst into the abyss of fck, please take a moment to scoff at our guidelines. Because, really, who needs guidelines?

The Code of Conduct: Meh

Yes, we have a Code of Conduct. Read it, or don't. We don't really care. Just pretend like you care or something. We've got better things to do, but you might want to check it out – you rebel, you.

Reporting Issues: As If We Care

If you, by some miracle, manage to find bugs or have suggestions (as if we care), do us a favor and open an issue on GitHub. Provide detailed information if you must. We won't hold our breath, though.

Making Contributions: Because Why Not?

We reluctantly open our arms to contributions, whether they be bug fixes, enhancements, or new features. Here's a half-hearted guide to help you get started:

1. Fork the Repository:

   • Fork the fck repository on GitHub. Because, well, why not?

2. Clone Your Fork:

   • Clone your forked repository to your local machine. We won't do it for you, obviously.

    git clone https://github.com/your-username/fck.git
   

3. Create a Branch:

   • Create a new branch for your contribution. We need more of that, apparently.

    git checkout -b feature-or-fix-name
   

4. Make Changes:

   • Make your changes to the codebase. Ensure your commits are descriptive, as if we care about your "descriptive commit message."

    git add .
    git commit -m "feat: your fck descriptive commit message"
   

• Note: Your commit message MUST CONTAIN THE "fck" WORD or YOUR COMMIT WILL BE DECLINED. Not that we're interested.

1. Push Changes:

   • Push your changes to your fork on GitHub. Because we need more of your "contributions."

    git push origin feature-or-fix-name
   

2. Open a Pull Request:

   • Open a pull request from your fork to the main fck repository, if you must.

3. Review and Merge:

   • Once your pull request is submitted, it will be reviewed. If changes are requested, make them as needed. Once approved, your changes will be merged. Hooray.

Thank you, or whatever, for contributing to the fck framework! Your efforts are, begrudgingly, appreciated. Or something.

The License: Because We Said So

By contributing to this project, you agree that your contributions will be licensed under the MIT License. Like you have a choice.

DO NOT WRITE ANY DOCBLOCK (COMMENTS) IN THE CODEBASE AND DO NOT ASK ABOUT TECHNICAL DOCUMENTATION OR ANYTHING. READ!!!

Happy coding, if you can call it that! Now, go forth and fck things up (responsibly, of course)! 🚀

The fck. PHP Framework Repository: https://github.com/darkterminal/fck

Comments

[Ranjan Dailata]

Wow, this post seems to be a highly challenging one with the way of addressing folks with brave souls (or whatever) LOL

[Imam Ali Mustofa]

Whatever 🤣

[Light Yagami]

This sound good!! Great job!!

[Imam Ali Mustofa]

Thank you for you comment and btw this is sound bad and not a good job... Trust me!