Entry points
Clicking the edit link on these places launches the Editor against that branch

• Creation (when there is no Jenkinsfile in the repository)
  • https://invis.io/Q2A110KM9#/216715766_Pipeline_Creation-Github_Step_4_No_Repos
  • https://zpl.io/AOIaW
• For a specific branch on the Branches tab
  • https://invis.io/Q2A110KM9#/218891868_Pipeline-Branches
  • https://zpl.io/ZtGMt8
• For a specific branch on the run screen
  • https://invis.io/Q2A110KM9#/218685699_Failed_Tests_1200px
  • https://zpl.io/Z4q3x2

• Existing functionality that lets you copy and paste the Jenkinsfile should be preserved as the "degrated" experience.

Saving

We present a dialog that allows users to:

• Specify a commit message
• Specify a commit description
• Radio list
  • Commit to $CURRENT_BRANCH
  • Commit to new branch
    • Text box: branch name - only show this text input if "commit to new branch" radio is selected
• Buttons
  • Save - commits the Jenkinsfile and triggers a rescan
  • Cancel - exists this dialog and returns to the editor

Design:

• • https://invis.io/Q2A110KM9#/219088047_Editor-Home
  • https://zpl.io/1Aij8a

Resolving scopes
When saving we may have to ask for a "upgrade" to the stored Github token or provide one if the user does not have one set (credentials are stored per user). Writing to the repository also requires different scopes than what we may have setup during creation. I'd imagine this looks very similar to the creation way of doing it (asking for a Key)

• https://invis.io/Q2A110KM9#/219318668_Editor-Commit_New_File_Connect_To_Github
• https://zpl.io/ZT8LLy