When is it better to just work in one feature branch than creating multiple












0















Background



I received the task to search for redundant jquery selectors in our code. Now, the files where our JS code is located is seperated into different modules.



My supervisor game me the task and told me that I should create a feature branch for each Module (sometimes it only contains 1 - 2 js files).



I'm struggling between doing it properly (like a programmer would) and being efficient without wasting to much time creating feature branches.



Question



Therefore my question: When should I create multiple feature branches and when only one to prevent an overkill?










share|improve this question





























    0















    Background



    I received the task to search for redundant jquery selectors in our code. Now, the files where our JS code is located is seperated into different modules.



    My supervisor game me the task and told me that I should create a feature branch for each Module (sometimes it only contains 1 - 2 js files).



    I'm struggling between doing it properly (like a programmer would) and being efficient without wasting to much time creating feature branches.



    Question



    Therefore my question: When should I create multiple feature branches and when only one to prevent an overkill?










    share|improve this question



























      0












      0








      0








      Background



      I received the task to search for redundant jquery selectors in our code. Now, the files where our JS code is located is seperated into different modules.



      My supervisor game me the task and told me that I should create a feature branch for each Module (sometimes it only contains 1 - 2 js files).



      I'm struggling between doing it properly (like a programmer would) and being efficient without wasting to much time creating feature branches.



      Question



      Therefore my question: When should I create multiple feature branches and when only one to prevent an overkill?










      share|improve this question
















      Background



      I received the task to search for redundant jquery selectors in our code. Now, the files where our JS code is located is seperated into different modules.



      My supervisor game me the task and told me that I should create a feature branch for each Module (sometimes it only contains 1 - 2 js files).



      I'm struggling between doing it properly (like a programmer would) and being efficient without wasting to much time creating feature branches.



      Question



      Therefore my question: When should I create multiple feature branches and when only one to prevent an overkill?







      svn branch feature-branch






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited 18 hours ago







      Gentle Sama

















      asked 20 hours ago









      Gentle SamaGentle Sama

      496




      496
























          0






          active

          oldest

          votes











          Your Answer






          StackExchange.ifUsing("editor", function () {
          StackExchange.using("externalEditor", function () {
          StackExchange.using("snippets", function () {
          StackExchange.snippets.init();
          });
          });
          }, "code-snippets");

          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "1"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54249555%2fwhen-is-it-better-to-just-work-in-one-feature-branch-than-creating-multiple%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          0






          active

          oldest

          votes








          0






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes
















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Stack Overflow!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54249555%2fwhen-is-it-better-to-just-work-in-one-feature-branch-than-creating-multiple%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          Homophylophilia

          Updating UILabel text programmatically using a function

          Cloud Functions - OpenCV Videocapture Read method fails for larger files from cloud storage