Quantcast

WFLY/WFCORE PRs

classic Classic list List threaded Threaded
8 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

WFLY/WFCORE PRs

kkhan
Please try to include a link to the Jira in the pull request when opening them. I want to be a good citizen and resolve them when merging, but it is a PITA to have to manually find the Jira issue in the absence of links.
_______________________________________________
wildfly-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: WFLY/WFCORE PRs

Brian Stansberry
I’ll try and be better about that. I used to count on Max Andersen's AutoLink browser extension (which was great!) to generate links from just the issue number text, but now Chrome has been updated to block extensions that aren’t from the Chrome Web Store. Grumble grumble.

> On Sep 1, 2016, at 5:07 AM, Kabir Khan <[hidden email]> wrote:
>
> Please try to include a link to the Jira in the pull request when opening them. I want to be a good citizen and resolve them when merging, but it is a PITA to have to manually find the Jira issue in the absence of links.
> _______________________________________________
> wildfly-dev mailing list
> [hidden email]
> https://lists.jboss.org/mailman/listinfo/wildfly-dev

--
Brian Stansberry
Manager, Senior Principal Software Engineer
JBoss by Red Hat




_______________________________________________
wildfly-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: WFLY/WFCORE PRs

Peter Palaga
It is still possible to load a non-Web Store extension in Chrome. I am
not 100% sure it works for the one from Max, it works for my [1] Jira
linker for sure. -- P

[1]
https://github.com/ppalaga/jboss-jira-content-script#jboss-jira-content-script

On 2016-09-01 15:37, Brian Stansberry wrote:

> I’ll try and be better about that. I used to count on Max Andersen's AutoLink browser extension (which was great!) to generate links from just the issue number text, but now Chrome has been updated to block extensions that aren’t from the Chrome Web Store. Grumble grumble.
>
>> On Sep 1, 2016, at 5:07 AM, Kabir Khan <[hidden email]> wrote:
>>
>> Please try to include a link to the Jira in the pull request when opening them. I want to be a good citizen and resolve them when merging, but it is a PITA to have to manually find the Jira issue in the absence of links.
>> _______________________________________________
>> wildfly-dev mailing list
>> [hidden email]
>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>

_______________________________________________
wildfly-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: WFLY/WFCORE PRs

Brian Stansberry
Thanks!

The install process shown on https://developer.chrome.com/extensions/getstarted#unpacked didn’t work for Max’s but it did for yours. :)

I suspect I could get Max’s to work if I stuck the js I have in its own dir and added a manifest.json that looks like yours. But instead I’ll try yours out now!

> On Sep 2, 2016, at 3:47 PM, Peter Palaga <[hidden email]> wrote:
>
> It is still possible to load a non-Web Store extension in Chrome. I am not 100% sure it works for the one from Max, it works for my [1] Jira linker for sure. -- P
>
> [1] https://github.com/ppalaga/jboss-jira-content-script#jboss-jira-content-script
>
> On 2016-09-01 15:37, Brian Stansberry wrote:
>> I’ll try and be better about that. I used to count on Max Andersen's AutoLink browser extension (which was great!) to generate links from just the issue number text, but now Chrome has been updated to block extensions that aren’t from the Chrome Web Store. Grumble grumble.
>>
>>> On Sep 1, 2016, at 5:07 AM, Kabir Khan <[hidden email]> wrote:
>>>
>>> Please try to include a link to the Jira in the pull request when opening them. I want to be a good citizen and resolve them when merging, but it is a PITA to have to manually find the Jira issue in the absence of links.
>>> _______________________________________________
>>> wildfly-dev mailing list
>>> [hidden email]
>>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>
>

--
Brian Stansberry
Manager, Senior Principal Software Engineer
JBoss by Red Hat




_______________________________________________
wildfly-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: WFLY/WFCORE PRs

Brian Stansberry
Peter, I just want to say thanks again for this; it’s working well. I appreciate how it opens the link in a new tab. I mostly use this when I’m working with pull requests, and it’s nice not to have the PR tab change.

For anyone on here who reviews pull requests, you should check out this browser extension.

> On Sep 6, 2016, at 1:17 PM, Brian Stansberry <[hidden email]> wrote:
>
> Thanks!
>
> The install process shown on https://developer.chrome.com/extensions/getstarted#unpacked didn’t work for Max’s but it did for yours. :)
>
> I suspect I could get Max’s to work if I stuck the js I have in its own dir and added a manifest.json that looks like yours. But instead I’ll try yours out now!
>
>> On Sep 2, 2016, at 3:47 PM, Peter Palaga <[hidden email]> wrote:
>>
>> It is still possible to load a non-Web Store extension in Chrome. I am not 100% sure it works for the one from Max, it works for my [1] Jira linker for sure. -- P
>>
>> [1] https://github.com/ppalaga/jboss-jira-content-script#jboss-jira-content-script
>>
>> On 2016-09-01 15:37, Brian Stansberry wrote:
>>> I’ll try and be better about that. I used to count on Max Andersen's AutoLink browser extension (which was great!) to generate links from just the issue number text, but now Chrome has been updated to block extensions that aren’t from the Chrome Web Store. Grumble grumble.
>>>
>>>> On Sep 1, 2016, at 5:07 AM, Kabir Khan <[hidden email]> wrote:
>>>>
>>>> Please try to include a link to the Jira in the pull request when opening them. I want to be a good citizen and resolve them when merging, but it is a PITA to have to manually find the Jira issue in the absence of links.
>>>> _______________________________________________
>>>> wildfly-dev mailing list
>>>> [hidden email]
>>>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>>
>>
>
> --
> Brian Stansberry
> Manager, Senior Principal Software Engineer
> JBoss by Red Hat
>
>
>
>
> _______________________________________________
> wildfly-dev mailing list
> [hidden email]
> https://lists.jboss.org/mailman/listinfo/wildfly-dev

--
Brian Stansberry
Manager, Senior Principal Software Engineer
JBoss by Red Hat




_______________________________________________
wildfly-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: WFLY/WFCORE PRs

Peter Palaga
Hi Brian, nice to hear that, thanks! If anybody spots a missing Jira/BZ
pattern, PRs are welcome. -- P

On 2016-09-16 14:21, Brian Stansberry wrote:

> Peter, I just want to say thanks again for this; it’s working well. I appreciate how it opens the link in a new tab. I mostly use this when I’m working with pull requests, and it’s nice not to have the PR tab change.
>
> For anyone on here who reviews pull requests, you should check out this browser extension.
>
>> On Sep 6, 2016, at 1:17 PM, Brian Stansberry <[hidden email]> wrote:
>>
>> Thanks!
>>
>> The install process shown on https://developer.chrome.com/extensions/getstarted#unpacked didn’t work for Max’s but it did for yours. :)
>>
>> I suspect I could get Max’s to work if I stuck the js I have in its own dir and added a manifest.json that looks like yours. But instead I’ll try yours out now!
>>
>>> On Sep 2, 2016, at 3:47 PM, Peter Palaga <[hidden email]> wrote:
>>>
>>> It is still possible to load a non-Web Store extension in Chrome. I am not 100% sure it works for the one from Max, it works for my [1] Jira linker for sure. -- P
>>>
>>> [1] https://github.com/ppalaga/jboss-jira-content-script#jboss-jira-content-script
>>>
>>> On 2016-09-01 15:37, Brian Stansberry wrote:
>>>> I’ll try and be better about that. I used to count on Max Andersen's AutoLink browser extension (which was great!) to generate links from just the issue number text, but now Chrome has been updated to block extensions that aren’t from the Chrome Web Store. Grumble grumble.
>>>>
>>>>> On Sep 1, 2016, at 5:07 AM, Kabir Khan <[hidden email]> wrote:
>>>>>
>>>>> Please try to include a link to the Jira in the pull request when opening them. I want to be a good citizen and resolve them when merging, but it is a PITA to have to manually find the Jira issue in the absence of links.
>>>>> _______________________________________________
>>>>> wildfly-dev mailing list
>>>>> [hidden email]
>>>>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>>>
>>>
>>
>> --
>> Brian Stansberry
>> Manager, Senior Principal Software Engineer
>> JBoss by Red Hat
>>
>>
>>
>>
>> _______________________________________________
>> wildfly-dev mailing list
>> [hidden email]
>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>

_______________________________________________
wildfly-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: WFLY/WFCORE PRs

Peter Palaga
Knowing that my Chrome extension for linking from GitHub to JBoss Jira
and Bugzilla has found some audience here, just a notice that the script
is getting improvements from time to time. I recently added an info to
the README [2] how to get notified about updates and how to update. -- P

[1]
https://github.com/ppalaga/jboss-jira-content-script#how-to-get-notified-about-updates

On 2016-09-16 14:53, Peter Palaga wrote:

> Hi Brian, nice to hear that, thanks! If anybody spots a missing Jira/BZ
> pattern, PRs are welcome. -- P
>
> On 2016-09-16 14:21, Brian Stansberry wrote:
>> Peter, I just want to say thanks again for this; it’s working well. I appreciate how it opens the link in a new tab. I mostly use this when I’m working with pull requests, and it’s nice not to have the PR tab change.
>>
>> For anyone on here who reviews pull requests, you should check out this browser extension.
>>
>>> On Sep 6, 2016, at 1:17 PM, Brian Stansberry <[hidden email]> wrote:
>>>
>>> Thanks!
>>>
>>> The install process shown on https://developer.chrome.com/extensions/getstarted#unpacked didn’t work for Max’s but it did for yours. :)
>>>
>>> I suspect I could get Max’s to work if I stuck the js I have in its own dir and added a manifest.json that looks like yours. But instead I’ll try yours out now!
>>>
>>>> On Sep 2, 2016, at 3:47 PM, Peter Palaga <[hidden email]> wrote:
>>>>
>>>> It is still possible to load a non-Web Store extension in Chrome. I am not 100% sure it works for the one from Max, it works for my [1] Jira linker for sure. -- P
>>>>
>>>> [1] https://github.com/ppalaga/jboss-jira-content-script#jboss-jira-content-script
>>>>
>>>> On 2016-09-01 15:37, Brian Stansberry wrote:
>>>>> I’ll try and be better about that. I used to count on Max Andersen's AutoLink browser extension (which was great!) to generate links from just the issue number text, but now Chrome has been updated to block extensions that aren’t from the Chrome Web Store. Grumble grumble.
>>>>>
>>>>>> On Sep 1, 2016, at 5:07 AM, Kabir Khan <[hidden email]> wrote:
>>>>>>
>>>>>> Please try to include a link to the Jira in the pull request when opening them. I want to be a good citizen and resolve them when merging, but it is a PITA to have to manually find the Jira issue in the absence of links.
>>>>>> _______________________________________________
>>>>>> wildfly-dev mailing list
>>>>>> [hidden email]
>>>>>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>>>>
>>>>
>>>
>>> --
>>> Brian Stansberry
>>> Manager, Senior Principal Software Engineer
>>> JBoss by Red Hat
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> wildfly-dev mailing list
>>> [hidden email]
>>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>
>
> _______________________________________________
> wildfly-dev mailing list
> [hidden email]
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>

_______________________________________________
wildfly-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: WFLY/WFCORE PRs

Brian Stansberry
I just updated. Thanks. :)

> On Nov 3, 2016, at 2:06 PM, Peter Palaga <[hidden email]> wrote:
>
> Knowing that my Chrome extension for linking from GitHub to JBoss Jira
> and Bugzilla has found some audience here, just a notice that the script
> is getting improvements from time to time. I recently added an info to
> the README [2] how to get notified about updates and how to update. -- P
>
> [1]
> https://github.com/ppalaga/jboss-jira-content-script#how-to-get-notified-about-updates
>
> On 2016-09-16 14:53, Peter Palaga wrote:
>> Hi Brian, nice to hear that, thanks! If anybody spots a missing Jira/BZ
>> pattern, PRs are welcome. -- P
>>
>> On 2016-09-16 14:21, Brian Stansberry wrote:
>>> Peter, I just want to say thanks again for this; it’s working well. I appreciate how it opens the link in a new tab. I mostly use this when I’m working with pull requests, and it’s nice not to have the PR tab change.
>>>
>>> For anyone on here who reviews pull requests, you should check out this browser extension.
>>>
>>>> On Sep 6, 2016, at 1:17 PM, Brian Stansberry <[hidden email]> wrote:
>>>>
>>>> Thanks!
>>>>
>>>> The install process shown on https://developer.chrome.com/extensions/getstarted#unpacked didn’t work for Max’s but it did for yours. :)
>>>>
>>>> I suspect I could get Max’s to work if I stuck the js I have in its own dir and added a manifest.json that looks like yours. But instead I’ll try yours out now!
>>>>
>>>>> On Sep 2, 2016, at 3:47 PM, Peter Palaga <[hidden email]> wrote:
>>>>>
>>>>> It is still possible to load a non-Web Store extension in Chrome. I am not 100% sure it works for the one from Max, it works for my [1] Jira linker for sure. -- P
>>>>>
>>>>> [1] https://github.com/ppalaga/jboss-jira-content-script#jboss-jira-content-script
>>>>>
>>>>> On 2016-09-01 15:37, Brian Stansberry wrote:
>>>>>> I’ll try and be better about that. I used to count on Max Andersen's AutoLink browser extension (which was great!) to generate links from just the issue number text, but now Chrome has been updated to block extensions that aren’t from the Chrome Web Store. Grumble grumble.
>>>>>>
>>>>>>> On Sep 1, 2016, at 5:07 AM, Kabir Khan <[hidden email]> wrote:
>>>>>>>
>>>>>>> Please try to include a link to the Jira in the pull request when opening them. I want to be a good citizen and resolve them when merging, but it is a PITA to have to manually find the Jira issue in the absence of links.
>>>>>>> _______________________________________________
>>>>>>> wildfly-dev mailing list
>>>>>>> [hidden email]
>>>>>>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>>>>>
>>>>>
>>>>
>>>> --
>>>> Brian Stansberry
>>>> Manager, Senior Principal Software Engineer
>>>> JBoss by Red Hat
>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> wildfly-dev mailing list
>>>> [hidden email]
>>>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>>
>>
>> _______________________________________________
>> wildfly-dev mailing list
>> [hidden email]
>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>
>
> _______________________________________________
> wildfly-dev mailing list
> [hidden email]
> https://lists.jboss.org/mailman/listinfo/wildfly-dev

--
Brian Stansberry
Manager, Senior Principal Software Engineer
JBoss by Red Hat




_______________________________________________
wildfly-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev
Loading...