Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Source Control, going offline, and trashing repos #603

Closed
Hosch250 opened this issue Jun 10, 2015 · 4 comments
Closed

Source Control, going offline, and trashing repos #603

Hosch250 opened this issue Jun 10, 2015 · 4 comments
Labels
enhancement Feature requests, or enhancements to existing features. Ideas. Anything within the project's scope. feature-source-control support Whether you're using Rubberduck or you've forked it and have questions, never hesitate to ask!

Comments

@Hosch250
Copy link
Member

I went to work on one of the issues with using Source Control offline. I had already set up Source Control for one document, so I figured I could open another document and start from there. Surprisingly, RD automatically assigned all my documents to the same repo in Source Control. So, you didn't give me a way to go back offline, so I closed Excel and trashed the repo in the File Explorer. Now, Source Control doesn't even open.
@Hosch250 Hosch250 added bug Identifies work items for known bugs feature-source-control labels Jun 10, 2015
@Hosch250
Copy link
Member Author

Deleting the SourceControl.rubberduck file fixed this, but don't like doing this.

@Hosch250
Copy link
Member Author

What I'd really like to happen here is to not auto-setup every doc on source control, and provide a way to remove individual repositories.

@Hosch250 Hosch250 added enhancement Feature requests, or enhancements to existing features. Ideas. Anything within the project's scope. feature-request and removed bug Identifies work items for known bugs labels Jun 10, 2015
@rubberduck203
Copy link
Member

What do you mean? Nothing gets "auto-setup". You have to create a repository from the active project for it to be attached to that project. I think maybe you created a repo from a project with the default "VBAProject" name. Then, when you created a new blank project (with a default name) RD got confused and said

Oh look! We have a repository for that project!

There's an issue to prevent people from creating repositories before they've named their project, but we've also been considering using the filename as a unique identifier.

@Hosch250
Copy link
Member Author

Oh, OK. Thank you for the clarification.

@rubberduck203 rubberduck203 added support Whether you're using Rubberduck or you've forked it and have questions, never hesitate to ask! and removed feature-request labels Mar 5, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement Feature requests, or enhancements to existing features. Ideas. Anything within the project's scope. feature-source-control support Whether you're using Rubberduck or you've forked it and have questions, never hesitate to ask!
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@rubberduck203 @Hosch250