The elegant git gui for dev teams
I’m kinda new to this hosting software externally. I’ve been happy using Gitlab for internal private projects, but recently I’ve been forking and reworking the work of others to include into my own.
Publishing up to github is pretty straight forward. Using git from the command line to just add, commit and push is all the same, just now with an online repository rather than the internal Gitlab. In fact once the repository is added to the project I’m betting the Atom.io built in Git will handle the committing and pushing.
Recently I decided to have a look at yarn – it uses the npmjs repository just like npm. So far I’m liking it. It’s kinda pretty and I do like the caching.
I pretty much use
yarn where ever I would have used
npm. So instead of
npm init I use
npm install I now use
yarn add. Where I used
npm run dev now it’s
yarn run dev, and
yarn run hot, etc.
Now to push my packages up to npmjs. First you have to have an npmjs account, so sign up. Like Github, npmjs is only free for “public” packages. If you want “private”, you have to pay.
Then link yarn and npm up to your npmjs account using login.
$ yarn login yarn login v1.7.0 question npm username: mynpmjsname question npm email: email@example.com Done in 32.16s.
Similarly for npm.
This saves an auth token into your
.npmrc file so if you’ve supplied the password already you won’t need it to publish with. What I found after pushing up to git and publishing to npmjs was that I was doing things in the wrong order. So used to doing git commit and push, it’s second nature.
Before you git push to github, publish the package to npmjs. Do it this way because it will force a version increment which will do a git commit. Because it will have incremented the version in your
The name, version and description etc. in your
package.json is what will be used by your project.
Because you are likely to want to publish what is probably a private project name (beginning with @) to a public project you’ll need to tell your publish command to make it public, or you’ll get a warning pretty much about about not having subscribed to publish private projects.
$ yarn publish --access=public
When you look at your projects in your npmjs.com profile you’ll see your fresh project ready for everyone to consume!
$ yarn publish yarn publish v1.7.0 [1/4] Bumping version... info Current version: 1.8.1 question New version: 1.8.2 info New version: 1.8.2 [2/4] Logging in... [3/4] Publishing... success Published. [4/4] Revoking token... info Not revoking login token, specified via config file. Done in 8.85s.
But that’s how easy it was to publish up to npmjs!
Now you’ve pushed to npmjs, you can do a
git push to deliver the same project up to Github.com now with the new version.
We have a distinct lack of version control in the relatively small development team that manages one of our business applications. One of the main challenges isn’t really related to the developers, but to the vendor that connects remotely and “fixes” things without leaving any clue as to what has been changed.
So I came up with a sneaky plan to deploy Git onto the servers and manage the versions of configuration files used by the application. I can then capture any changes and roll back as necessary.
I’ve had a few little dealings with Github in the past as a contributor, but thought as I’m working on a project that borrows from a lot of code that is “sociably” hosted on Github by many Open Source developers, I thought I’d take the opportunity to put something back.
So what is Github?
It’s a location for Gits! So more importantly what is Git? Git is a version control mechanism that allows you to manage and maintain a folder structure, recording and monitoring changes as you develop. So Github is an online repository to publish your Gits.
Once published the whole world can see your code and your changes. Not only that they can clone your work, make changes and submit the changes back to you for inclusion in your project.