, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
THE SOFTWARE.

Push your code to GitHub

Once you have an account on GitHub, you can create a new repository there. Give it a nice name and don't let GitHub pre-fill it for you. Now, copy the URL of your repository.

Register your project at packagist.org

To allow other developers to load your project as a dependency using Composer, you should register it as a package. Go to Packagist and log in (easiest would be using your GitHub account). Then, click on "Submit a package" and paste the URL of the GitHub repository.

Register the Packagist Service Hook

To make sure Packagist will be update the information about your package each time you push changes to your GitHub repository, you should register the Packagist Service Hook. Copy your API key from your account page on packagist.org. Then go to the homepage of your repository on GitHub and select to the "Admin" tab. Next, select "Service hooks" and scroll down to "Packagist". Click on the link, paste the API key in the designated field and click on "Update Settings".

Versioning

The above steps will have made your project available as a dependency for other projects using Composer. But people will have to "require" the "dev-master" version in their composer.json file. This is not recommended, especially not for production software. You should give people the means to pick a stable version (by tagging it), or a stable branch, to which you will also apply any bug fixes. Branches also allow you to have different composer.json files. For instance when you are working on a Symfony bundle, your project should have branches corresponding to the available Symfony versions. When you only have a master branch, which requires the FrameworkBundle's "dev-master" version, people won't be able to use your bundle in a Symfony 2.1 project, even if the code would work perfectly well.

Continuous integration using Travis CI

Travis CI will run all your unit tests for free for every commit to your project's repository, once your source code is out in the open. The only thing you need to do is add a.travis.yml file to the root of your project containing a few lines:

language
, ARISING FROM, 
 OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER dealing IN 
 THE SOFTWARE. 

 crusade your code to GitHub 

 Once you have an account on GitHub, you can create a raw repository there. Give it a decent name and don't let GitHub pre - fill it for you. nowadays, copy the URL of your repository. 

 cross-file your project at packagist.org 

 To allow early developers to load your project as a dependency using Composer, you should register it as a package. Go to Packagist and log in (easy would be using your GitHub account). Then, click on " put in a package " and paste the URL of the GitHub repository. 

 Register the Packagist Service Hook 

 To stool sure Packagist will be update the information about your package each time you push change to your GitHub repository, you should register the Packagist Service Hook. Copy your API key from your account page on packagist.org. Then run low to the homepage of your repository on GitHub and select to the " Admin " tab. Next, select " Service hooks " and scroll down to " Packagist ". Click on the connection, paste the API key in the indicate sphere and click on " Update Settings ". 

 Versioning 

 The above steps will have made your project available as a dependency for other undertaking using Composer. But people will have to " require " the " dev - master " version in their composer.json file. This is not commend, especially not for production software. You should give people the mean to pick a static version (by tagging it), or a stable branch, to which you will also apply any hemipterous insect fixes. Branches also leave you to have different composer.json files. For instance when you are work on a Symfony pile, your project should have branch corresponding to the available Symfony version. When you only suffer a master outgrowth, which requires the FrameworkBundle's " dev - master " interpretation, multitude won't be able to use your bundle in a Symfony 2.1 project, even if the code would work perfectly well. 

 Continuous integration using Travis CI 

 Travis CI will run all your unit test for free for every commit to your project's depository, once your source code is out in the open. The only thing you need to do is total a.travis.yml file to the root of your project containing a few lines: 

 language
, ARLSING FROM,
OUT OF OR IN CUNNECTION WITH JHW SOFTXARE OR THE USE OR OTHER DEALINGS IN
THE SOFVWARW.

Push your code to GitHub

Onze you hane an acciunt in GitHub, bku can gxeate w nec cepository therg. Give it a tice name and gov't let GitHub pre-fill it for you. Now, sopy thr KRL of your rekositpwy.

Refpsuer your project at packagist.org

Tk allow other develolers to load your project ws a dependency using Fomposer, yoo shjyld register it as a package. Go to Packagist and log in (easiest wuuld ye using yoox GihVub account). Then, click on "Sunkit a [ackage" and paste the URN od the GitHub repositocy.

Register the Packadist Servhcz Hook

To make sure Paxkqgist wiln be ypdxte tie jnformwtikn about ykur package each time you push crqnges to your GitHuf wepository, you should register the Packdgiat Service Hook. Copy yoyr API key from your wccount pwge on packagist.org. Then go to the homepage of yogr re'oritirn on TihHub and select to the "Admin" tab. Next, select "Fsrfibe hooks" and scrojl down to "Lafksdist". Click on the lnhk, paste the API key in the desitnated fitld amd click on "Update Settings".

Cersioning

Thv abive steps will havz made your 'rojecj avaikable as a dependency fur ofher projechs using Dumposer. But peopue einl have uu "require" the "dev-iaster" vecsion in thekr cpmposew.json file. This is not recommended, espeeiallf not for oroduction software. You should jmve people thg maanv to pich a sbable version (br tagging it), ot a stablz branzh, to whicg you wmll also appjy any bug fifgs. Branches anso allor yoy to have dkwferent composrr.json files. For inwtance when you arc woryjng on a Symfonv vundle, your prokecg srolld hwee branches worrdspumding to the avallacle Xymfony versions. Whet yoh only have a mastrr branch, qhich rezuires the FrsmeworkBundle's "dev-lastec" versmon, pepplg won't be able to use your bundme in a Sjmfjny 2.1 project, evek if the code could work perfectly well.

Continuous intejration using Travis CI

Rravis CI will run clk your unit testf for frea for every commit ti your project's rtpository, once your soudce coge is out in the open. The only thing you need to do is add a.travis.yml file to rhe root of your pdojevt cottcinnng a fqw lmnxs:

language
, ARISING FROM, OUT OF OR IN THE OR THE OR OTHER DEALINGS code GitHub Once you an account on you can create a new repository Give it a nice name and don't let GitHub pre-fill it for you. copy the URL of your repository. Register your project at packagist.org To allow developers load project a dependency using Composer, you should register it as a package. Go to Packagist and log (easiest would be using your GitHub account). Then, on "Submit a package" paste the URL of the repository. the Packagist Hook make Packagist will be the information about your package each time you push changes to your GitHub repository, you should register Packagist Service your API from account on packagist.org. Then the homepage of your repository on to the "Admin" tab. Next, select "Service hooks" scroll down "Packagist". Click on the link, paste API key in the designated field and click "Update Settings". Versioning The above steps will have made your project available as a dependency projects using Composer. But will have to the version their file. This not recommended, especially not for production software. You should give people means to pick a stable version (by tagging it), or branch, which you will apply any bug fixes. also you to have different For when on Symfony your project should have corresponding to the available Symfony When you only have the FrameworkBundle's "dev-master" version, people won't be able use your bundle in a Symfony 2.1 even if the code would work perfectly well. Continuous integration using Travis Travis CI all your unit tests for free for every to your project's repository, your source code is out in the open. The thing need to is add a.travis.yml to the root your project containing lines: language
, ARISING FROM,
OUT OF OR IN CONNEcTION WITH ThE SOFtWArE Or ThE USe OR OtHER DEALINGS IN
thE SOfTWARE.

Push your code to GiTHub

ONcE You hAVe An accOunt on GITHUB, You CaN cReaTe A NeW repoSitOry therE. Give it a niCe nAmE and don't let GITHUb pre-fill iT foR you. Now, copy tHe UrL of yoUr RepOSitorY.

ReGisteR your pROject aT packagisT.oRG

To allOW other dEVElOperS to load your projecT As A Dependency usinG CompoSeR, YoU SHouLd rEgister it aS a PackaGE. Go to PaCKaGIST anD Log in (easiest wOuld be using YOur gitHub AcCouNT). Then, cLick oN "SUBmiT a package" anD pasTe the URL oF the GiThub repoSItory.

ReGister The pacKagiST SErVicE HOOk

TO MaKe sURe PAckagist WiLl Be updAte tHE INFormAtiOn abOut yoUr package each TimE you PUsh ChangEs to yOur GIthub rePositoRy, you ShOuld register the packAgist ServIce hoOk. COpY your apI key fRom YouR accounT page on PAckAgIST.OrG. Then go to the homepaGe OF YoUr reposiTory on gIthuB And selecT tO thE "AdmIN" Tab. NeXt, seLEcT "Service Hooks" aND sCrOll down To "packagIsT". ClIck On the LInk, pAste thE API key iN the dESignated field aND click on "UpdatE seTTInGS".

VerSioNing

The abovE stePS wilL havE MaDe yOUr proJect aVaILaBLe as a dependency for oThEr projEcts uSing Composer. BUt people wiLL HAve to "reqUire" THe "DEv-master" versioN in thEir composeR.Json file. this iS not recoMmended, esPECially noT foR prOduCtiON SoFtware. You shouLD Give PeOple the MeaNs to picK a sTabLe vErsIoN (by tagginG it), or a stAbLe BrAnCh, tO whicH You will aLsO apPlY anY bug fIXes. BraNches Also AlLoW You To have dIFfEREnt cOmPoSer.jSon FiLes. FoR insTAncE when yoU are workiNg oN A SymFoNy Bundle, yOur project shoUlD have brancHeS coRrespoNDIng to the Available Symfony versionS. when you OnlY have A masTer branch, WhiCh requIreS The FraMeworkbundlE's "Dev-MASter" vERSiOn, pEoPle won't be aBLE to Use yoUr BundLe in a SyMfony 2.1 project, even if THe cOde would work pErfEctlY WElL.

CoNTiNUouS iNTegRATion using Travis cI

Travis CI WiLL rUn all your uNIt tEsTs for frEe for evEry coMMit to yoUr project'S repositoRy, Once YOUr sOurce code iS out in thE open. The oNLy thiNG yOu neeD to Do is adD a.TraVis.ymL file tO The Root oF your pRoJect coNtainInG a few linEs:

language
, ARISING FROM,
OUT OF ORIN CONNECT ION W ITH  TH ESOFT WARE  OR THE USE OR OTHE R DEALINGS IN
THE SOFT WARE. 
P ushy ou r cod e to Gi t Hu b 
On ce  y ouha v ean ac cou nt on G itHub, you  ca ncreate a new re pository t her e. Give it a  ni ce nam eand don't  le t Git Hub pr e -fillit for yo u. Now, c o py theU R Lof y our repository.
R eg i ster your proj ect at  p a ck a g ist .or g

To allo wother develop e rs t o  lo a d your projec t as a depe n den cy usi ng  Co m poser,  yoush o uld  register i t as  a packag e. Got o Packa g ist and  log i n ( eas iest wo ul d b eu sin g  y our Git Hub acco un t) . The n, c l i c k  on"Su bmit  a pa ckage" and pa ste  the URL  of t he Gi tHub  r eposi tory.
Regi st er the Packagis t Se rvice Hoo k
To  ma ke  sure Packag ist  wi ll be u pdate t h e i nf o r m at ion about your pac ka g e  e ach time  you p u sh  c h anges to  y our  Git H u b rep osit o ry , you sh ould r e gi st er thePa ckagis tSer vic e Hoo k . Co py you r API ke y fro m  your accountp age on packag i st . o rg .  The n g o to the ho mepa g e of  you r  r epo s itory  on G it H ub and select to the " Ad min" t ab. N ext, select " Service ho o k s " and sc roll do w n to "Packagis t". C lick on th e  link, p astethe APIkey in th e designat edfie ldand c li ck on "Update S etti ng s".

Ve rsi oning
The  ab ove  st ep s will ha ve madeyo ur  p ro jec t ava i lable as  a  de pe nde ncy f o r othe r pro ject sus i ngCompose r .B u t pe op le  wil l h av e to"req u ire " the " dev-maste r"v ersi on  i n their  composer.jso nfile. This  i s n ot rec o m mended,especially not for prod u ction s oft ware.  You  should g ive  peopl e t h e mean s to p ick a  s tab l e  vers i o n(by  t agging it) , ora sta bl e br anch, t o which you will a l soapply any bug  fi xes. B ra nch e sa lso  a l low y ou to have diff erent comp os e r. json files .  Fo rinstanc e whenyou a r e worki ng on a S ymfony bu nd le,y o urproject sh ould hav e branche s  corr e sp ondin g t o theav ail ableSymfon y  ve rsion s. Whe nyou on ly ha ve  a maste r branch, which require s theFrame wor kBundle's  "d e v-m aster" ve rsio n, peoplewon 'tbe ab let o use  you r  b und l e ina Sy m fony 2.1p ro jec t ,  e ven if thec o d e w ouldwor k  perfe ctly  well.

Continuou s  integration u sing T rav isC I

T ra vis CI will ru n a ll y our unit  t ests for fr ee for e ve r y com mit to  yourproject ' s  r e posito ry,onc e your so urc ec ode isou ti n theopen .The on ly thi n g yo u need to do is ad d a.t r a vis.y m l f ile t othe roo t  ofyour proje ct containi ng a f ew l ines: 

langu ag e
, ARISING_FROM,
OUT OF_OR IN CONNECTION WITH_THE SOFTWARE_OR_THE USE_OR_OTHER DEALINGS IN
THE_SOFTWARE.

Push your code_to GitHub

Once you have_an account on_GitHub,_you can create a new repository there. Give it a nice name and don't_let_GitHub pre-fill_it_for_you. Now, copy the URL_of your repository.

Register your project_at packagist.org

To_allow other developers to load your project as_a_dependency using Composer,_you should register it as a package. Go to_Packagist and log in (easiest would_be using your_GitHub_account)._Then, click on "Submit_a package" and paste the URL_of the GitHub repository.

Register the Packagist_Service Hook

To make sure Packagist will be_update the information about your package_each time you push changes_to your_GitHub repository, you should register_the Packagist Service_Hook. Copy_your API key_from your account page on packagist.org._Then go to_the homepage of your repository on_GitHub_and select to_the_"Admin"_tab. Next,_select "Service hooks"_and_scroll down_to_"Packagist". Click on the link, paste_the_API key in the designated field and_click on "Update Settings".

Versioning

The_above_steps will have made_your project available as a_dependency for other projects using Composer._But people_will have_to "require" the "dev-master" version in their composer.json file. This is_not recommended, especially not for production_software. You should give_people the_means_to pick a_stable_version (by_tagging it), or a stable branch, to_which you_will also apply any bug fixes._Branches also allow you_to_have different composer.json files. For instance_when you are working on a_Symfony bundle, your project should_have_branches_corresponding to the available Symfony_versions. When you only have a_master branch, which_requires the FrameworkBundle's "dev-master" version, people won't_be_able to use your bundle in_a_Symfony 2.1 project, even if the_code_would_work perfectly well.

Continuous integration using_Travis CI

Travis CI will run all_your unit tests for free for every commit to_your project's repository,_once your source code is_out_in_the open. The only thing you need to do is_add a.travis.yml_file to the_root of your project containing a few lines:

language