Learning Git
-
I use Gitlab because of the built in runners. It's nice to have the CI/CD pipeline built directly in.
Jenkins and others obviously work with Github but being able to have a local system do the testing (that's automatically kicked off) while using the hosted Gitlab is pretty awesome.
I also use VS code and Atom (with the Git Plus package).
-
Free Plan Comparison
-
@tim_g said in Learning Git:
I use VS Code with GitLab.
I need to install VS code. on my desktop. been hearing you two complement it.
-
@jaredbusch said in Learning Git:
@tim_g said in Learning Git:
I use VS Code with GitLab.
I need to install VS code. on my desktop. been hearing you two complement it.
It's pretty nice. The built in Git stuff is nicer than Atom. To me it feels faster than Atom also.
-
@jaredbusch said in Learning Git:
@tim_g said in Learning Git:
I use VS Code with GitLab.
I need to install VS code. on my desktop. been hearing you two complement it.
It's like Atom but with some benefits (and drawbacks.) If you like Atom and use it mostly for coding, VS Code might be the right choice for you.
-
@Bundy-Associates uses Bitbucket for now. But we are at the 5 collaborator max, so if we need to add a new collaborator I will take the time to move it all to Gitlab.
-
@scottalanmiller said in Learning Git:
@jaredbusch said in Learning Git:
@tim_g said in Learning Git:
I use VS Code with GitLab.
I need to install VS code. on my desktop. been hearing you two complement it.
It's like Atom but with some benefits (and drawbacks.) If you like Atom and use it mostly for coding, VS Code might be the right choice for you.
How well is the support for powershell in Atom? That's mainly the reason why I use VS Code for PowerShell.
-
Atom + bitbucket here. Unless I'm allowed to do open source, then github.
-
We use Bitbucket here. It is super cheap for small teams. We got JIRA and Bitbucket full versions running on in house servers with support for under $100 a year if you have less than 10 users.
-
@s-hackleman said in Learning Git:
We use Bitbucket here. It is super cheap for small teams. We got JIRA and Bitbucket full versions running on in house servers with support for under $100 a year if you have less than 10 users.
GitLab is free for large teams. What's "cheap" when compared to free?
-
@scottalanmiller said in Learning Git:
@jaredbusch said in Learning Git:
@tim_g said in Learning Git:
I use VS Code with GitLab.
I need to install VS code. on my desktop. been hearing you two complement it.
It's like Atom but with some benefits (and drawbacks.) If you like Atom and use it mostly for coding, VS Code might be the right choice for you.
@stacksofplates said in Learning Git:
@jaredbusch said in Learning Git:
@tim_g said in Learning Git:
I use VS Code with GitLab.
I need to install VS code. on my desktop. been hearing you two complement it.
It's pretty nice. The built in Git stuff is nicer than Atom. To me it feels faster than Atom also.
matter of taste: I've used both for coding (mostly python) and I prefer Atom. As far as git is concerned I feel constrained with both and I go straight to cmd line.
-
@matteo-nunziati said in Learning Git:
@scottalanmiller said in Learning Git:
@jaredbusch said in Learning Git:
@tim_g said in Learning Git:
I use VS Code with GitLab.
I need to install VS code. on my desktop. been hearing you two complement it.
It's like Atom but with some benefits (and drawbacks.) If you like Atom and use it mostly for coding, VS Code might be the right choice for you.
@stacksofplates said in Learning Git:
@jaredbusch said in Learning Git:
@tim_g said in Learning Git:
I use VS Code with GitLab.
I need to install VS code. on my desktop. been hearing you two complement it.
It's pretty nice. The built in Git stuff is nicer than Atom. To me it feels faster than Atom also.
matter of taste: I've used both for coding (mostly python) and I prefer Atom. As far as git is concerned I feel constrained with both and I go straight to cmd line.
I generally use the command line too for GIT. Just so quick and easy, and works every time.
-
@scottalanmiller said in Learning Git:
@matteo-nunziati said in Learning Git:
@scottalanmiller said in Learning Git:
@jaredbusch said in Learning Git:
@tim_g said in Learning Git:
I use VS Code with GitLab.
I need to install VS code. on my desktop. been hearing you two complement it.
It's like Atom but with some benefits (and drawbacks.) If you like Atom and use it mostly for coding, VS Code might be the right choice for you.
@stacksofplates said in Learning Git:
@jaredbusch said in Learning Git:
@tim_g said in Learning Git:
I use VS Code with GitLab.
I need to install VS code. on my desktop. been hearing you two complement it.
It's pretty nice. The built in Git stuff is nicer than Atom. To me it feels faster than Atom also.
matter of taste: I've used both for coding (mostly python) and I prefer Atom. As far as git is concerned I feel constrained with both and I go straight to cmd line.
I generally use the command line too for GIT. Just so quick and easy, and works every time.
I find the integrations in the apps quicker for normal commits. Don't have to switch between the app and a terminal (or even switch to a terminal in the app). The shortcuts are quick, and auto-complete as you type. I've never not had it work.
-
Here's an example of how quick it is:
I can't figure out how to get the gif to work correctly.
-
@stacksofplates said in Learning Git:
@scottalanmiller said in Learning Git:
@matteo-nunziati said in Learning Git:
@scottalanmiller said in Learning Git:
@jaredbusch said in Learning Git:
@tim_g said in Learning Git:
I use VS Code with GitLab.
I need to install VS code. on my desktop. been hearing you two complement it.
It's like Atom but with some benefits (and drawbacks.) If you like Atom and use it mostly for coding, VS Code might be the right choice for you.
@stacksofplates said in Learning Git:
@jaredbusch said in Learning Git:
@tim_g said in Learning Git:
I use VS Code with GitLab.
I need to install VS code. on my desktop. been hearing you two complement it.
It's pretty nice. The built in Git stuff is nicer than Atom. To me it feels faster than Atom also.
matter of taste: I've used both for coding (mostly python) and I prefer Atom. As far as git is concerned I feel constrained with both and I go straight to cmd line.
I generally use the command line too for GIT. Just so quick and easy, and works every time.
I find the integrations in the apps quicker for normal commits. Don't have to switch between the app and a terminal (or even switch to a terminal in the app). The shortcuts are quick, and auto-complete as you type. I've never not had it work.
Quake style terminals are perfect for this. Hit a hot key, terminal is in your face, commit, hotkey and it is gone again.
-
@quixoticjustin said in Learning Git:
@stacksofplates said in Learning Git:
@scottalanmiller said in Learning Git:
@matteo-nunziati said in Learning Git:
@scottalanmiller said in Learning Git:
@jaredbusch said in Learning Git:
@tim_g said in Learning Git:
I use VS Code with GitLab.
I need to install VS code. on my desktop. been hearing you two complement it.
It's like Atom but with some benefits (and drawbacks.) If you like Atom and use it mostly for coding, VS Code might be the right choice for you.
@stacksofplates said in Learning Git:
@jaredbusch said in Learning Git:
@tim_g said in Learning Git:
I use VS Code with GitLab.
I need to install VS code. on my desktop. been hearing you two complement it.
It's pretty nice. The built in Git stuff is nicer than Atom. To me it feels faster than Atom also.
matter of taste: I've used both for coding (mostly python) and I prefer Atom. As far as git is concerned I feel constrained with both and I go straight to cmd line.
I generally use the command line too for GIT. Just so quick and easy, and works every time.
I find the integrations in the apps quicker for normal commits. Don't have to switch between the app and a terminal (or even switch to a terminal in the app). The shortcuts are quick, and auto-complete as you type. I've never not had it work.
Quake style terminals are perfect for this. Hit a hot key, terminal is in your face, commit, hotkey and it is gone again.
I use the drop down terminal extension for GNOME3 a lot. I'm just lazy and like typing as little as possible
-
@stacksofplates said in Learning Git:
@quixoticjustin said in Learning Git:
@stacksofplates said in Learning Git:
@scottalanmiller said in Learning Git:
@matteo-nunziati said in Learning Git:
@scottalanmiller said in Learning Git:
@jaredbusch said in Learning Git:
@tim_g said in Learning Git:
I use VS Code with GitLab.
I need to install VS code. on my desktop. been hearing you two complement it.
It's like Atom but with some benefits (and drawbacks.) If you like Atom and use it mostly for coding, VS Code might be the right choice for you.
@stacksofplates said in Learning Git:
@jaredbusch said in Learning Git:
@tim_g said in Learning Git:
I use VS Code with GitLab.
I need to install VS code. on my desktop. been hearing you two complement it.
It's pretty nice. The built in Git stuff is nicer than Atom. To me it feels faster than Atom also.
matter of taste: I've used both for coding (mostly python) and I prefer Atom. As far as git is concerned I feel constrained with both and I go straight to cmd line.
I generally use the command line too for GIT. Just so quick and easy, and works every time.
I find the integrations in the apps quicker for normal commits. Don't have to switch between the app and a terminal (or even switch to a terminal in the app). The shortcuts are quick, and auto-complete as you type. I've never not had it work.
Quake style terminals are perfect for this. Hit a hot key, terminal is in your face, commit, hotkey and it is gone again.
I use the drop down terminal extension for GNOME3 a lot. I'm just lazy and like typing as little as possible
With a tiny BASH wrapper, you could have essentially no typing at all. Something like "gitcom these are my changes" and it submits for you. Or just alias it to "g".
-
@quixoticjustin said in Learning Git:
@stacksofplates said in Learning Git:
@quixoticjustin said in Learning Git:
@stacksofplates said in Learning Git:
@scottalanmiller said in Learning Git:
@matteo-nunziati said in Learning Git:
@scottalanmiller said in Learning Git:
@jaredbusch said in Learning Git:
@tim_g said in Learning Git:
I use VS Code with GitLab.
I need to install VS code. on my desktop. been hearing you two complement it.
It's like Atom but with some benefits (and drawbacks.) If you like Atom and use it mostly for coding, VS Code might be the right choice for you.
@stacksofplates said in Learning Git:
@jaredbusch said in Learning Git:
@tim_g said in Learning Git:
I use VS Code with GitLab.
I need to install VS code. on my desktop. been hearing you two complement it.
It's pretty nice. The built in Git stuff is nicer than Atom. To me it feels faster than Atom also.
matter of taste: I've used both for coding (mostly python) and I prefer Atom. As far as git is concerned I feel constrained with both and I go straight to cmd line.
I generally use the command line too for GIT. Just so quick and easy, and works every time.
I find the integrations in the apps quicker for normal commits. Don't have to switch between the app and a terminal (or even switch to a terminal in the app). The shortcuts are quick, and auto-complete as you type. I've never not had it work.
Quake style terminals are perfect for this. Hit a hot key, terminal is in your face, commit, hotkey and it is gone again.
I use the drop down terminal extension for GNOME3 a lot. I'm just lazy and like typing as little as possible
With a tiny BASH wrapper, you could have essentially no typing at all. Something like "gitcom these are my changes" and it submits for you. Or just alias it to "g".
True. I usually don't alias much. But I think we are at the point where you are writing things to get the cli at the same speed as what's in the applications.
-
@stacksofplates said in Learning Git:
@quixoticjustin said in Learning Git:
@stacksofplates said in Learning Git:
@quixoticjustin said in Learning Git:
@stacksofplates said in Learning Git:
@scottalanmiller said in Learning Git:
@matteo-nunziati said in Learning Git:
@scottalanmiller said in Learning Git:
@jaredbusch said in Learning Git:
@tim_g said in Learning Git:
I use VS Code with GitLab.
I need to install VS code. on my desktop. been hearing you two complement it.
It's like Atom but with some benefits (and drawbacks.) If you like Atom and use it mostly for coding, VS Code might be the right choice for you.
@stacksofplates said in Learning Git:
@jaredbusch said in Learning Git:
@tim_g said in Learning Git:
I use VS Code with GitLab.
I need to install VS code. on my desktop. been hearing you two complement it.
It's pretty nice. The built in Git stuff is nicer than Atom. To me it feels faster than Atom also.
matter of taste: I've used both for coding (mostly python) and I prefer Atom. As far as git is concerned I feel constrained with both and I go straight to cmd line.
I generally use the command line too for GIT. Just so quick and easy, and works every time.
I find the integrations in the apps quicker for normal commits. Don't have to switch between the app and a terminal (or even switch to a terminal in the app). The shortcuts are quick, and auto-complete as you type. I've never not had it work.
Quake style terminals are perfect for this. Hit a hot key, terminal is in your face, commit, hotkey and it is gone again.
I use the drop down terminal extension for GNOME3 a lot. I'm just lazy and like typing as little as possible
With a tiny BASH wrapper, you could have essentially no typing at all. Something like "gitcom these are my changes" and it submits for you. Or just alias it to "g".
True. I usually don't alias much. But I think we are at the point where you are writing things to get the cli at the same speed as what's in the applications.
I've not found any application that comes close in speed to the "up arrow, hit enter" speed of the CLI, though.
-
@quixoticjustin said in Learning Git:
@stacksofplates said in Learning Git:
@quixoticjustin said in Learning Git:
@stacksofplates said in Learning Git:
@quixoticjustin said in Learning Git:
@stacksofplates said in Learning Git:
@scottalanmiller said in Learning Git:
@matteo-nunziati said in Learning Git:
@scottalanmiller said in Learning Git:
@jaredbusch said in Learning Git:
@tim_g said in Learning Git:
I use VS Code with GitLab.
I need to install VS code. on my desktop. been hearing you two complement it.
It's like Atom but with some benefits (and drawbacks.) If you like Atom and use it mostly for coding, VS Code might be the right choice for you.
@stacksofplates said in Learning Git:
@jaredbusch said in Learning Git:
@tim_g said in Learning Git:
I use VS Code with GitLab.
I need to install VS code. on my desktop. been hearing you two complement it.
It's pretty nice. The built in Git stuff is nicer than Atom. To me it feels faster than Atom also.
matter of taste: I've used both for coding (mostly python) and I prefer Atom. As far as git is concerned I feel constrained with both and I go straight to cmd line.
I generally use the command line too for GIT. Just so quick and easy, and works every time.
I find the integrations in the apps quicker for normal commits. Don't have to switch between the app and a terminal (or even switch to a terminal in the app). The shortcuts are quick, and auto-complete as you type. I've never not had it work.
Quake style terminals are perfect for this. Hit a hot key, terminal is in your face, commit, hotkey and it is gone again.
I use the drop down terminal extension for GNOME3 a lot. I'm just lazy and like typing as little as possible
With a tiny BASH wrapper, you could have essentially no typing at all. Something like "gitcom these are my changes" and it submits for you. Or just alias it to "g".
True. I usually don't alias much. But I think we are at the point where you are writing things to get the cli at the same speed as what's in the applications.
I've not found any application that comes close in speed to the "up arrow, hit enter" speed of the CLI, though.
You still have to enter your message. So to me it's the same as hotkey and then message.
