Uploaded image for project: 'IGB'
  1. IGB
  2. IGBF-2373

Move transcript isoform App into a separate repository

    Details

    • Type: Task
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Labels:
    • Story Points:
      0.25
    • Sprint:
      Spring 8 : 24 Apr to 8 May, Spring 8 : 11 May to 25 May, Spring 9 : 25 May to 8 Jun, Summer 1: 8 Jun - 19 Jun

      Description

      Following previously describe workflows, migrate transcript isoform app from the "experimental apps" repository into a separate repository just for this one app.

      As before, preserve the commit history of the app.

      See similar, related issues for tips on how to do this, if required. This was most recently done for the NCBI Primer App by Pooja Nikhare.

      Please note:

      This should be done only after IGBF-2123 code has been merged into master.

        Attachments

          Issue Links

            Activity

            Hide
            ann.loraine Ann Loraine added a comment -

            Thanks for the feedback Logan Weidenhammer !

            Show
            ann.loraine Ann Loraine added a comment - Thanks for the feedback Logan Weidenhammer !
            Hide
            ann.loraine Ann Loraine added a comment -

            Ready for PR.

            Show
            ann.loraine Ann Loraine added a comment - Ready for PR.
            Hide
            rweidenh Logan Weidenhammer (Inactive) added a comment -

            Should I create a pull request from my fork's master branch to the lab's master even though the topic branch pipeline does not build?

            The POM needs to be reconfigured.

            Show
            rweidenh Logan Weidenhammer (Inactive) added a comment - Should I create a pull request from my fork's master branch to the lab's master even though the topic branch pipeline does not build? The POM needs to be reconfigured.
            Hide
            ann.loraine Ann Loraine added a comment -

            Changes should always be made on a topic branch, which you then push to your fork. You then issue a PR from the topic branch on your fork to the master branch on the team repo.

            Can you let me know if there is misleading documentation about that somewhere?

            Show
            ann.loraine Ann Loraine added a comment - Changes should always be made on a topic branch, which you then push to your fork. You then issue a PR from the topic branch on your fork to the master branch on the team repo. Can you let me know if there is misleading documentation about that somewhere?
            Hide
            rweidenh Logan Weidenhammer (Inactive) added a comment -

            I think the documentation is good. The problem for me was understanding the effect of rebasing versus merging, so I did some reading on that. Confirming that the topic branch is used to create a pull request directly to the master branch on the team repo does help a lot.

            Show
            rweidenh Logan Weidenhammer (Inactive) added a comment - I think the documentation is good. The problem for me was understanding the effect of rebasing versus merging, so I did some reading on that. Confirming that the topic branch is used to create a pull request directly to the master branch on the team repo does help a lot.

              People

              • Assignee:
                Unassigned
                Reporter:
                ann.loraine Ann Loraine
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: