[JIRA] (JENKINS-41550) Tell user where to get github token

2017-02-19 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41550  
 
 
  Tell user where to get github token   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Sprint: 
 1.0  
 

  
 
 
 
 

 
 
 

 
 
 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.


[JIRA] (JENKINS-41550) Tell user where to get github token

2017-02-09 Thread mne...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 already fixed with WIP  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-41550  
 
 
  Tell user where to get github token   
 

  
 
 
 
 

 
Change By: 
 Michael Neale  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 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.


[JIRA] (JENKINS-41550) Tell user where to get github token

2017-02-07 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41550  
 
 
  Tell user where to get github token   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Sprint: 
 iapetus  
 

  
 
 
 
 

 
 
 

 
 
 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.


[JIRA] (JENKINS-41550) Tell user where to get github token

2017-02-07 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41550  
 
 
  Tell user where to get github token   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Sprint: 
 panthalassa  
 

  
 
 
 
 

 
 
 

 
 
 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.


[JIRA] (JENKINS-41550) Tell user where to get github token

2017-01-29 Thread mne...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41550  
 
 
  Tell user where to get github token   
 

  
 
 
 
 

 
Issue Type: 
  Story  
 
 
Assignee: 
 Cliff Meyers  
 
 
Components: 
 blueocean-plugin  
 
 
Created: 
 2017/Jan/30 5:26 AM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Michael Neale  
 

  
 
 
 
 

 
 With the github creation flow, one is required to get or create a token. Generally this means creating a new token.  A simple informational link to: https://github.com/settings/tokens/new could help shortcut this process for people unfamiliar with it. Additional copy saying "repo" and "user:email" scopes are required at a minimum could help too (the validation messages will shout at them if they miss something required though).   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment