Download the PHP package dashifen/git-branch without Composer

On this page you can find all versions of the php package dashifen/git-branch. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Informations about the package git-branch

Git Branch

An object that encapsulates information embedded in my branch naming scheme.

Based~~ on the success of a similar scheme that I use professionally, for newer personal projects, I've decided to be more precise in the way that I name Git branches. Instead of naming them whatever I want when I create them, I'll be prefixing them with pertinent information as in 220622f-new-feature or 220622b-bugfix.

The first six digits are the date in YYMMDD format followed by either one of the following: r, f, or b. These correspond to a release, feature, or bugfix branch respectively. Following those data, a short description (what might have been the entire branch name in the past) is included as well.

Encoding these data into the branch name helps with semantic versioning. At a glance, I can see how to alter the version number based on the type of the branch. And, the date helps me to know when I started a branch which may help to know how to merge things.

Branched Branches

If I need to branch a "child" branch off a "parent," then the child's name follows the parent's preceded by 2 hyphens, e.g. 220622f-parent--child. This isn't strictly necessary; a child branch could simply be named as above. But, the order of merges might become a bit more messy without a record of what was branched off of what.

All versions of git-branch with dependencies

PHP Build Version
Package Version
Requires dashifen/exception Version ^1.2
dashifen/repository Version ^4.0
phlak/semver Version ^4.0
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package dashifen/git-branch contains the following files

Loading the files please wait ....