[JIRA] (JENKINS-41966) Entering and exiting the editor

[bmacl...@cloudbees.com (JIRA)]

Title: Message Title

Brody Maclean updated an issue   Jenkins / JENKINS-41966 Entering and exiting the editor Change By: Brody Maclean *Entry points* * 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 *Saving options* Very similar to Githubs web file editing workflow. ** https://invis.io/Q2A110KM9#/219103950_Editor-Commit_New_File ** https://zpl.io/ZGeB17 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 * Buttons ** Save - commits the Jenkinsfile ** Cancel - exists this dialog and returns to the editor _Github example_ !github-new-file.png|thumbnail! *Authenticating* When saving we may have to ask for a "upgrade" to the stored Github token. Writing to the repository needs 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) *Editor header buttons* * * https://invis.io/Q2A110KM9#/219088047_Editor-Home ** https://zpl.io/1Aij8a * Save - triggers the save dialog * Try ** Needs to be defined* * Cancel - exists the editor without saving, goes back to entry point Add Comment   This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.