LogFAQs > #942074596

LurkerFAQs, Active DB, DB1, DB2, DB3, DB4, DB5, Database 6 ( 01.01.2020-07.18.2020 ), DB7, DB8, DB9, DB10, DB11, DB12, Clear

Topic List	Page List: 1
Topic	Why is GitHub always deeply awful to do anything in.
Sahuagin 07/13/20 9:19:47 PM #20:	EclairReturns posted... I see that this is a possibility. But sometimes, I am very obsessive about folder and filenames, and such, and will have great difficulty deleting old folders and files should I rename them and commit them once more to my repository. The old files with the old names will remain even after committing the new, updated files. And it just creates a lot of clutter, you see. If I want to remove it, I'd have to go into every single one of my files in order to delete them one-by-one. I know that complaining about and insulting a new program/video game just because I am not adept at learning it is not mature in the slightest. But I suppose I must get used to knowing the site structure and such; I myself am a newcomer to the site, and have not researched its features thoroughly enough to make any unwarranted judgements. I don't know git and github, but as others have said, it should just be an online git repo. the "right" way to use it (or, one way to use it), is to have the source files on your PC, commit them to a local repo on your machine, and then push updates from your local repo to the online repo. the online repo is the "central" repo that everyone working on the project pushes to and pulls from, but is not the working repo; each user would have their own working repo. (to some degree you must already know this, since you need to have the files on your local machine to build them; I guess you could push/pull your changes directly to and from the online repo, but I think it would be better to have a local one. (you should have a local one anyway when you clone it in the first place). otherwise, not sure what you're missing. maybe you are missing a step when deleting files? you would delete the files from your drive, then maybe tell git that these missing files should be marked as removed (may or may not need that step not sure), then commit. if the files come back then you probably haven't told git that the files should be removed. (another way to do this might be just to tell git that the file should be deleted, and let git delete it. this is where I'd have to know git specifics to go any further.)) --- *The truth basks in scrutiny.* https://imgur.com/GMouTGs http://projecteuler.net/profile/Sahuagin.png <cite>Sahuagin posted [p:942074596] in Why is Git... [t:78840925]...</cite> <quote>EclairReturns posted... </cite> <quote>I see that this is a possibility. But sometimes, I am very obsessive about folder and filenames, and such, and will have great difficulty deleting old folders and files should I rename them and commit them once more to my repository. The old files with the old names will remain even after committing the new, updated files. And it just creates a lot of clutter, you see. If I want to remove it, I'd have to go into every single one of my files in order to delete them one-by-one. I know that complaining about and insulting a new program/video game just because I am not adept at learning it is not mature in the slightest. But I suppose I must get used to knowing the site structure and such; I myself am a newcomer to the site, and have not researched its features thoroughly enough to make any unwarranted judgements.</quote>I don't know git and github, but as others have said, it should just be an online git repo. the "right" way to use it (or, one way to use it), is to have the source files on your PC, commit them to a local repo on your machine, and then push updates from your local repo to the online repo. the online repo is the "central" repo that everyone working on the project pushes to and pulls from, but is not the working repo; each user would have their own working repo. (to some degree you must already know this, since you need to have the files on your local machine to build them; I guess you could push/pull your changes directly to and from the online repo, but I think it would be better to have a local one. (you should have a local one anyway when you clone it in the first place). otherwise, not sure what you're missing. maybe you are missing a step when deleting files? you would delete the files from your drive, then maybe tell git that these missing files should be marked as removed (may or may not need that step not sure), then commit. if the files come back then you probably haven't told git that the files should be removed. (another way to do this might be just to tell git that the file should be deleted, and let git delete it. this is where I'd have to know git specifics to go any further.)) --- The truth basks in scrutiny. https://imgur.com/GMouTGs http://projecteuler.net/profile/Sahuagin.png</quote> ... Copied to Clipboard!
Topic List	Page List: 1