Branch: refs/heads/master
  Home:   https://github.com/jenkinsci/blueocean-pipeline-editor-plugin
  Commit: 8a4b1363a9e52256edd5c04298a2c092c09f5af8
      
https://github.com/jenkinsci/blueocean-pipeline-editor-plugin/commit/8a4b1363a9e52256edd5c04298a2c092c09f5af8
  Author: Cliff Meyers <cliff.mey...@gmail.com>
  Date:   2017-08-15 (Tue, 15 Aug 2017)

  Changed paths:
    M src/main/js/EditorPage.jsx
    M src/main/js/SaveApi.js
    A src/main/js/api/ScmContentApi.js
    A src/main/js/api/TypedError.js
    M src/main/less/editor.less

  Log Message:
  -----------
  Story/jenkins 42791 editor prompt GitHub token (#45)

* add a class responsible for REST API calls ot the /scm/content API and 
formalize the errors the UI will try to handle

* WIP of porting the editor to use new ScmContentApi abstraction

* continued WIP to display "token dialog" when editing pipeline without 
credential

* style tweaks to token dialog

* fix a bug where the "conflict" dialog failed to show due to original request 
body not being available to UI error handler

* fix a bug where the indexing for GHE pipelines wouldn't work correctly due to 
wrong apiUrl being passed. ensure credential is always loaded and pass 
credentialId explicitly to "index" method

* delint

* simplify editor loading flow so it doesn't require credentialId before 
fetching "defaultBranch" via scm/orgs/repos API; credentialId no needed when 
reindexing either

* fix a bug that was preventing the error dialog from showing

* defend against "branch=undefined" query parameter being passed to 
/scm/content API

* remove unused method

* use status code === 428 to trigger credential prompt since string messages 
are prone to change

* polish, especially for github enterprise


-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Commits" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-commits+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to