If you say that they “won’t play nicely”, it makes it sound like you can’t have both packages installed at once because they have a negative interaction. They have absolutely no interaction or knowledge of each other’s existence, so how they play together is a non-question because, even though we can imagine it, from the code’s perspective it’s a physical impossibility. That’s all. What you want can be done, but someone would have to write a package to do it. It wouldn’t be a difficult package to write (you’re just automating a very predictable command line string with a little user input, using the tried and tested
git programs), but it might not be worth it when there’s a package in
process-palette that can automate any instruction you give it. Do you want thirty packages that all basically do one thing, or one package that can do anything?
I was wondering if this is a reason the files in the Git window are not changing from green to orange when modified. The truth may be that I’m not yet fully understanding the Git/GitHub extension per se. It’s also the case that, when modifying a file from the left-hand, Project tree, I can’t get them to change to orange in the Git window either…
You don’t actually have a remote repo for that folder. Everything is “green” in the Git tab because there are no remote files, so everything is a new file. Nothing is colored in
tree-view and you don’t have the “git repo” icon next to the
Context directory name because there’s no remote. You need to open the command line and run
git add remote origin followed by the address of your repo on GitHub or Bitbucket or whatever you use. Then run
git push -u origin to affirmatively tell git to push everything to the
origin and everything should work swell. I’ve done this a bunch of times. Then again, for that to work you have to actually have all of your files on your computer, and you just want to touch them with FTP.
One more note: Make sure that the repo you have remotely is either exactly the same project or completely blank. If you try to hook the wrong repos together, git will complain a lot even if the code files are identical. This is because it doesn’t look at the code, but at the commit hashes stored in the
Which may prompt me to wonder about the whole relationship between the local folder (“Project”) and the Remote view via remote-ftp.
The local folder is
Context/. And it doesn’t have any relationship, except that things you download from your FTP server are going to end up there. The tab you keep calling “Project” is the tree view. It’s entitled such because it is the tab where you go to look at all the folders that are a part of the active project (in Atom’s world, that’s everything you have open in a particular window).
… so it’s not clear to me how to create or link to a GitHub repository. How do I do that?
I recommend checking out GitHub’s documentation.
Thanks. The other two seem more appealing given they employ a tree structure on the left.
atom-commander can’t do a tree, but all you have to do to get a dock item to the left side is click on the tab and drag it up to the tab bar on the left dock.