|
I've been having a hell of a time trying to send all my git commits to an empty subversion repo. There are some pages I found through Google, but their instructions don't work with the newest versions of git. Any help?
|
#
¿
May 5, 2009 18:05
|
|
|
|
| # ¿ May 5, 2024 05:41 |
|
|
It's a local save system that complements Time Machine. I wouldn't depend on it as an actual VCS; if it were an actual VCS, it would lack a lot of features offered by most VCSs today.
|
|
#
¿
Jun 8, 2011 01:57
|
|
|
I have a relatively populated and active GitHub, and it hasn't helped much with my job search.
|
|
#
¿
Jul 18, 2013 02:30
|
|
|
https://enterprise.github.com/pricing 30 people means 10k (they sell 20 users per license). Still expensive.
|
|
#
¿
Oct 22, 2013 03:14
|
|
|
DSauer posted:I had completely forgotten that with Windows 8.1 Skydrive is integrated into the Window's file system and for all intents and purposes acts like any other folder on your PC. I was thinking of using it as a private repository rather than hosting my code on Bitbucket and the sort and Git doesn't seem to mind or even notice that its working on a remote folder located somewhere else in the world. Is there anything about this that would make it a dumb idea that I'm not seeing? Looks like this works fine with Google Drive as well from what I can see. I did the same thing but with Dropbox. It works fine, but don't treat any of the cloud file sync services as backup. They can and will sync corrupted data if your hardware goes bad. Also you may want to turn on two factor authentication on your Microsoft account depending how valuable your code is. Then make sure your account recovery methods are current, because that bit me in the rear end and I lost access to Dropbox and GitHub amongst many other accounts.
|
|
#
¿
Jan 17, 2014 16:43
|
|
|
as long as you don't use the sharing features of your preferred cloud sync software anywhere within your development directories, it's perfectly fine for personal development needs.
|
|
#
¿
Jan 21, 2014 20:00
|
|
|
Your VCS and you will go nuts once modifications are made in a shared folder. Imagine trying to work on separate branches. If you aren't using VCS, then it works fine until two or more people edit a file at the same time. You might be confusing my terminology, but most cloud sync services allow you to mark a folder as shared and others can edit it. Sharing a read-only link is perfectly fine; you're the only one that can edit the file. wolffenstein fucked around with this message at 22:22 on Jan 21, 2014 |
|
#
¿
Jan 21, 2014 22:19
|
|
|
RICHUNCLEPENNYBAGS posted:I'm using Git. How do you guys handle configuration with sensitive data (connection strings, passwords, etc.)? Especially if you want different configuration for each branch? shell environment variables seem like a decent way to do it if that's an option.
|
|
#
¿
Apr 18, 2014 04:03
|
|
|
So my dev shop has been only using Subversion to track the latest changes to code, and our production websites is just manually updated files. It's horrendous and leads to a lot of issues, so I'm trying to instate Git Flow as the standard methodology. However I'm still not sure how exactly to incorporate it into an already existing environment, especially when production is hardly in sync with the development branch. Any ideas or experiences to share?
|
|
#
¿
Dec 31, 2014 22:14
|
|
|
How exactly did you do that? Set up a branch for each one then attempt a merge?
|
|
#
¿
Jan 22, 2015 23:43
|
|
|
I did an svn move to reorganize a repo's contents into the standard trunk, tags, and branches layout. So far the only way I've found to update other working copies is svn switch --ignore-ancestry. I'm guessing that's all to it?
|
|
#
¿
Feb 14, 2015 19:52
|
|
|
They are separate commands. In bash, && shows a second command to run if the first is successful. Use whatever the PowerShell equivalent is or run each command. Or install Linux.
|
|
#
¿
Feb 18, 2015 14:18
|
|
|
Thermopyle posted:I'm completely unfamiliar with SVN, but an application I use distributes itself via SVN (lol). svn revert file1 file2
|
|
#
¿
May 24, 2015 18:49
|
|
|
since you probably don't care about the branch after you've looked at it, you can delete it with code:
|
|
#
¿
Aug 4, 2015 15:47
|
|
|
Yes.
|
|
#
¿
Oct 18, 2016 06:39
|
|
|
|
| # ¿ May 5, 2024 05:41 |
|
|
You can change which branch is displayed by default in your repo's GitHub settings.
|
|
#
¿
Jul 19, 2017 12:27
|
|