Feedback for git support + the new GitHub integration
replitjeremy (60)

Hi All!
Git support + the new integration with GitHub is in the process of rolling out!
When the feature is enabled for you, we'd love to hear how we could improve, and what additions you'd like to see.

feedback so far:

from @mat1:
"is there a way to create a .gitignore file? I tried making one but nothing happens when I press enter."

We're working on supporting this soon!

from @Vandesm14:
"Is this live? I don't see the git sidebar. Is this an explorer-only feature?"

We're currently in the process of rolling the feature out to everyone. Some users have it enabled currently.

You are viewing a single comment. View All
PaoloAmoroso (131)

@replitjeremy I've played a bit with the new version control features and they're so cool and well designed my grin doesn't want to go away. Here are some initial impressions and suggestions.

I'd prefer to optionally not access any organizations and related repos I'm a member of but I don't own. And I'd like to pick which email address to use for commits among the ones registered with GitHub.

When creating a repo it would be useful for to optionally add a well stuffed, language-sepcific .gitignore and file (like GitHub offers at repo creation), as well as a LICENSE file with the default license (MIT, if I recall correctly).

When the REPL detects changes to the source files and the repo origin is, there's a Commit & Push button in the commit dialog. Maybe I'm not too familiar with the Git/GitHub jargon and the way these tools work, but I'd expect the action to also synchronize (push?) the local changes with the remote GitHub repo. Instead I have to switch the origin to GitHub and click Push in the commit dialog.

This is a minor source of confusion though and, once clarified, it's no longer an issue.

replitjeremy (60)

Hey @PaoloAmoroso, thanks for all the great feedback!

I'll try to break it all down and address it here:
1. accessing orgs/non-owned repos

We'll only ever access repositories that you connect to on, and will never do anything related to GitHub data without an explicit action on your side. Also, if you don't own or have push access to a repo, we won't have permission to let you edit that code from either :)
pick an email address to use with GitHub
We are planning to support this!
.gitignore,, and a LICENSE file
we'll be adding support for hidden files soon, which will allow us to give the option to auto-include a .gitignore
currently working on a checkbox to add a README when you connect to GitHub
great call on the license file, I'll look into that
confusion about pushing locally vs. to GitHub
We're removing the dropdown, so that once you connect to GitHub, any push will go there as well without requiring extra user action.

PaoloAmoroso (131)

@replitjeremy Thanks for the clarifications and updates, here are some additional thoughts.

I misunderstood the required access permissions when connecting my GitHub account. Now it makes sense.

Removing the dropdown should indeed streamline and clarify the workflow.

PaoloAmoroso (131)

@replitjeremy The dropdown is gone from my test REPL, now there's a Connect to GitHub button. After clicking it I click Create GitHub repository and get the error Unable to create a GitHub repository Let us know if there is an issue. The GitHub repo I initially created from is still on GitHub.

replitjeremy (60)

@PaoloAmoroso Are you trying to create a repository with the same name of an existing one on GitHub? The GitHub API prevents us from doing that.

If you'd like to create a new repl that links to an existing GitHub Repo, add the github URL as a part of the 'new repl' form.

PaoloAmoroso (131)

@replitjeremy I actually did nothing special after setting up a fresh REPL to test's new version control features.

I created a fresh REPL, went through the version control set up flow to give access to my GitHub account and create the repo there, and did a few commits. When I came back to the REPL after you said you were going to remove the dropdown, the dropdown was indeed gone and clicking the option to connect to GitHub issued the error I mentioned earlier.