![]() The way I use this often is to start with a clean GIT commit, then play around learning new things in current project and when I have figured it out I will roll back ALL uncommitted changes back to my known commit state. I guess in essence these new files are not in GIT yet so really don’t see why they shouldn’t be deleted when the user has selected them to be deleted? This behaviour is disorienting and confusing to an end user as without knowing the “how it is supposed to work” causes trust concerns as to what is rolled back and what is not, hence why I started using GitKraken for this function.įrom what I gather it is also different behaviour to the way GIT intended it to be used, at least when I look at how GitKraken does it, but by no means am I a GIT expert. Then through GIT (refer to my screenshot in earlier post) on delete the routes file is rolled back, but the new file remains in place effectively orphaned until a new route is created? Look at this situation in a nodejs project: lets say a new file is added, the routes file is updated to reflect the new route. We are using VSTS currently, and when attempting to check in, I get several warnings of missing files.I think the way it currently stands is confusing, and incorrect. Now that it is running however, I need to check the entire solution into our source control. I'm trying to use mojoPortal for a new project I have started, and have had no troubles downloading and getting it running. Dev Series 31 Feature Packaging and Deployment.Dev Series 27 Implementing the update method.Dev Series 26 Enforcing Security Part 2.Dev Series 25 Enforcing Security Part 1.Dev Series 21 Protecting Against Untrusted Content.Dev Series 20 Default Button and Input Validation.Dev Series 19 Using a WYSIWYG Editor and Captcha.Dev Series 17 Upgrading from svn and Converting to VS 2010.Dev Series 16 Form Layout and Data Binding.Dev Series 14 First Guestbook Submission.Dev Series 13 Generate the Business Layer.Dev Series 12 Generating a Data Access Class.Dev Series 11 Using The Setup System to Run Upgrade Scripts.Dev Series 10 Create a Table Using the Setup System.Dev Series 2 Source Code Overview Part 2.Dev Series 1 Source Code Overview Part 1.Logging to the mojoPortal log4net log From Custom Code.Using Saved Query Data in a Custom Module.Controlling The CSS Used in the Editors.Producing a Minimal Build Without Features.Using a Different Database for a Feature.Adding Custom Items to the Administration Menu.Overview of Content Feature Development.Setting Up a Solution for Custom Development.Building a Simple PayPal Buy Now Feature.Allowing Users To Post Images In The Forums. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |