Is True?

An amazing useful function to check if true

Our ADVANTAGES

• 100% code coverage
• 100% safe code
• Zero dependencies

Support

You can buy me a coffee btw: https://buymeacoffee.com/ayalor

Contributing Guidelines

Basic guidelines

All packages you commit or submit by pull-request should follow these simple guidelines:

• Package a version which is still maintained by the upstream author and will be updated regularly with supported versions.
• Have no dependencies outside the is_exp_true core packages or this repository feed.
• Have been tested to compile with the correct includes and dependencies. Please also test with "Compile with full language support" found under "General Build Settings" set if language support is relevant to your package.
• Best of all -- it works as expected!

Commits in your pull-requests should

• Have a useful description prefixed with the package name (E.g.: "foopkg: Add libzot dependency")

Advice on pull requests

Pull requests are the easiest way to contribute changes to git repos at Github. They are the preferred contribution method, as they offer a nice way for commenting and amending the proposed changes.

• You need a local "fork" of the Github repo.

• Use a "feature branch" for your changes. That separates the changes in the pull request from your other changes and makes it easy to edit/amend commits in the pull request. Workflow using "feature_x" as the example:

  • Update your local git fork to the tip (of the master, usually)
  • Create the feature branch with git checkout -b feature_x
  • Edit changes and commit them locally
  • Push them to your Github fork by git push -u origin feature_x. That creates the "feature_x" branch at your Github fork and sets it as the remote of this branch
  • When you now visit Github, you should see a proposal to create a pull request

• If you later need to add new commits to the pull request, you can simply commit the changes to the local branch and then use git push to automatically update the pull request.

• If you need to change something in the existing pull request (e.g. to add a missing signed-off-by line to the commit message), you can use git push -f to overwrite the original commits. That is easy and safe when using a feature branch. Example workflow:

  • Checkout the feature branch by git checkout feature_x
  • Edit changes and commit them locally. If you are just updating the commit message in the last commit, you can use git commit --amend to do that
  • If you added several new commits or made other changes that require cleaning up, you can use git rebase -i HEAD~X (X = number of commits to edit) to possibly squash some commits
  • Push the changed commits to Github with git push -f to overwrite the original commits in the "feature_x" branch with the new ones. The pull request gets automatically updated

If you have commit access

• Do NOT use git push --force.
• Do NOT commit to other maintainer's packages without their consent.
• Use Pull Requests if you are unsure and to suggest changes to other maintainers.

Gaining commit access

• We will gladly grant commit access to responsible contributors who have made useful pull requests and / or feedback or patches to this repository or is_exp_true in general. Please include your request for commit access in your next pull request or ticket.

Release Branches

• Old stable branches were named after the following pattern "for-XX.YY" (e.g. for-14.07) before the LEDE split. During the LEDE split there was only one release branch with the name "lede-17.01". After merging the LEDE fork with is_exp_true the release branches are named according to the following pattern "is_exp_true-XX.YY" (e.g. is_exp_true-18.06).
• These branches are built with the respective is_exp_true release and are created during the release stabilisation phase.
• Please ONLY cherry-pick or commit security and bug-fixes to these branches.
• Do NOT add new packages and do NOT do major upgrades of packages here.
• If you are unsure if your change is suitable, please use a pull request.

Common LICENSE tags (short list)

(Complete list can be found at: https://spdx.org/licenses)

| Full Name | Identifier | | ------------------------------------------------ | :----------------------- | | Apache License 1.0 | Apache-1.0 | | Apache License 1.1 | Apache-1.1 | | Apache License 2.0 | Apache-2.0 | | Artistic License 1.0 | Artistic-1.0 | | Artistic License 1.0 w/clause 8 | Artistic-1.0-cl8 | | Artistic License 1.0 (Perl) | Artistic-1.0-Perl | | Artistic License 2.0 | Artistic-2.0 | | BSD 2-Clause "Simplified" License | BSD-2-Clause | | BSD 2-Clause FreeBSD License | BSD-2-Clause-FreeBSD | | BSD 2-Clause NetBSD License | BSD-2-Clause-NetBSD | | BSD 3-Clause "New" or "Revised" License | BSD-3-Clause | | BSD with attribution | BSD-3-Clause-Attribution | | BSD 3-Clause Clear License | BSD-3-Clause-Clear | | BSD 4-Clause "Original" or "Old" License | BSD-4-Clause | | BSD-4-Clause (University of California-Specific) | BSD-4-Clause-UC | | BSD Protection License | BSD-Protection | | GNU General Public License v1.0 only | GPL-1.0-only | | GNU General Public License v1.0 or later | GPL-1.0-or-later | | GNU General Public License v2.0 only | GPL-2.0-only | | GNU General Public License v2.0 or later | GPL-2.0-or-later | | GNU General Public License v3.0 only | GPL-3.0-only | | GNU General Public License v3.0 or later | GPL-3.0-or-later | | GNU Lesser General Public License v2.1 only | LGPL-2.1-only | | GNU Lesser General Public License v2.1 or later | LGPL-2.1-or-later | | GNU Lesser General Public License v3.0 only | LGPL-3.0-only | | GNU Lesser General Public License v3.0 or later | LGPL-3.0-or-later | | GNU Library General Public License v2 only | LGPL-2.0-only | | GNU Library General Public License v2 or later | LGPL-2.0-or-later | | Fair License | Fair | | ISC License | ISC | | MIT License | MIT | | No Limit Public License | NLPL | | OpenSSL License | OpenSSL | | X11 License | X11 | | zlib License | Zlib |

this whole lib is a fucking joke go grab a cofee with ur friends dude