Contributing to a GitHub repository - a bit stuck

evroom

Great!

Then a final question:

In short:

I program using in VS Code and here is Source Control active.
Can I use the GitHub CLI and the Visual Studio Code like together, or will they bite each other ?

A bit longer, with an example:

I have edited HoymilesWifi.sh in VS Code.
On my machine, I see:

% git status
On branch evroom
Your branch is up to date with 'origin/evroom'.

Changes not staged for commit:
  (use "git add <file>..." to update what will be committed)
  (use "git restore <file>..." to discard changes in working directory)
	modified:   HoymilesWifi.sh

no changes added to commit (use "git add" and/or "git commit -a")

On VS Code I see:

V Commit

Changes

$ HoymilesWifi.sh

Can I Commit it from within VS Code, or is it safer to use the GitHub CLI as I have done for the README.md file previously ?

sdetweil

@evroom you can use VSCode to do the commit and push…

I have not moved myself to that part of VSCode… (or let any IDE handle my commits etc)

mumblebaj

@evroom Just launch a terminal in VsCode

Make sure it is set to bash.

Then you can run the same commands git add and git commit -m "your commit text" and git push from the terminal.

sdetweil

@mumblebaj yes, was trying not to add too much extra as there is already a terminal window open for running MM with the modified module

evroom

@mumblebaj said in Contributing to a GitHub repository - a bit stuck:

Make sure it is set to bash.

It is set to zsh.
No issue to change it to bash, but is there a reasoning behind it ?

Stupidly enough I had this Terminal open the whole time.

I just did ‘Commit’ from within VS Code and then did ‘Sync Changes’.

Result:

% git status
On branch evroom
Your branch is up to date with 'origin/evroom'.

nothing to commit, working tree clean

So that works just fine.

I also made a change using the Terminal and then did the add and commit from the Terminal.
In the Source Control pane you can see what you do on the command line in real time.