Hi:
I've seen that several authors have included an appveyor.yml file in their repos. Personally, I failed to do this until I found Abdels configuration file. I use it for several add-ons and it's comfortable for me when posting releases. Should we upload it to the nvdaaddons organization, like Addons Wizzard, Potluck or Addon Template? It could be just a gist instead of a full repo. If so, I will do it during this week, if Abdel agrees and people is interested. Comments are appreciated
Cheers
|
|
Hi Noelia,
Thanks.
I agree.
For the instructions of use of the Appveyor service, for those who start, I think it would be also interesting to add a small explanation in the Wiki, as well as on the obtaining of a personal token for the use of the Github API.
A link to the Github help page for example.
Otherwise, the version of Python used in the appveyor.yml file is 2.7 32 bits, but it is not really useful to adapt it for Python 3, since the goal is just to build the add-on.
Cheers, Abdel.
toggle quoted message
Show quoted text
Le 23/10/2017 à 22:16, Noelia Ruiz a écrit : Hi:
I've seen that several authors have included an appveyor.yml file in their repos. Personally, I failed to do this until I found Abdels configuration file. I use it for several add-ons and it's comfortable for me when posting releases. Should we upload it to the nvdaaddons organization, like Addons Wizzard, Potluck or Addon Template? It could be just a gist instead of a full repo. If so, I will do it during this week, if Abdel agrees and people is interested. Comments are appreciated
Cheers
|
|
Sure. We can provide an explanation too. I think that Derek was the first person on the add-ons list to suggest this, and at start I was reluctant to use it, since I thought that it wouldn't provide too much benefit, but especially if we mantain various add-ons, even from different computers, where we perhaps don't have the necessary dependencies installed, is really useful. I will upload the appveyor file with the explanation when I can, perhaps the next weekend, if nobody can do it befor.
Cheers
2017-10-24 7:17 GMT+02:00, Abdel <abdelkrim.bensaid@...>:
toggle quoted message
Show quoted text
Hi Noelia,
Thanks.
I agree.
For the instructions of use of the Appveyor service, for those who start, I think it would be also interesting to add a small explanation in the Wiki, as well as on the obtaining of a personal token for the use of the Github API.
A link to the Github help page for example.
Otherwise, the version of Python used in the appveyor.yml file is 2.7 32 bits, but it is not really useful to adapt it for Python 3, since the goal is just to build the add-on.
Cheers, Abdel.
Le 23/10/2017 à 22:16, Noelia Ruiz a écrit :
Hi:
I've seen that several authors have included an appveyor.yml file in their repos. Personally, I failed to do this until I found Abdels configuration file. I use it for several add-ons and it's comfortable for me when posting releases. Should we upload it to the nvdaaddons organization, like Addons Wizzard, Potluck or Addon Template? It could be just a gist instead of a full repo. If so, I will do it during this week, if Abdel agrees and people is interested. Comments are appreciated
Cheers
|
|
toggle quoted message
Show quoted text
El 24/10/2017 a las 11:21, Noelia Ruiz escribió: Sure. We can provide an explanation too. I think that Derek was the first person on the add-ons list to suggest this, and at start I was reluctant to use it, since I thought that it wouldn't provide too much benefit, but especially if we mantain various add-ons, even from different computers, where we perhaps don't have the necessary dependencies installed, is really useful. I will upload the appveyor file with the explanation when I can, perhaps the next weekend, if nobody can do it befor. Cheers 2017-10-24 7:17 GMT+02:00, Abdel <abdelkrim.bensaid@...>:
Hi Noelia,
Thanks.
I agree.
For the instructions of use of the Appveyor service, for those who start, I think it would be also interesting to add a small explanation in the Wiki, as well as on the obtaining of a personal token for the use of the Github API.
A link to the Github help page for example.
Otherwise, the version of Python used in the appveyor.yml file is 2.7 32 bits, but it is not really useful to adapt it for Python 3, since the goal is just to build the add-on.
Cheers, Abdel.
Le 23/10/2017 à 22:16, Noelia Ruiz a écrit :
Hi:
I've seen that several authors have included an appveyor.yml file in their repos. Personally, I failed to do this until I found Abdels configuration file. I use it for several add-ons and it's comfortable for me when posting releases. Should we upload it to the nvdaaddons organization, like Addons Wizzard, Potluck or Addon Template? It could be just a gist instead of a full repo. If so, I will do it during this week, if Abdel agrees and people is interested. Comments are appreciated
Cheers
|
|
toggle quoted message
Show quoted text
Le 26/10/2017 à 22:02, Noelia Ruiz a écrit : Hi Abdel and everyone, please review this and provide feed-back or request changes if needed:
https://github.com/nvdaaddons/nvdaaddons.github.io/wiki/appveyor
Thanks
El 24/10/2017 a las 11:21, Noelia Ruiz escribió:
Sure. We can provide an explanation too. I think that Derek was the first person on the add-ons list to suggest this, and at start I was reluctant to use it, since I thought that it wouldn't provide too much benefit, but especially if we mantain various add-ons, even from different computers, where we perhaps don't have the necessary dependencies installed, is really useful. I will upload the appveyor file with the explanation when I can, perhaps the next weekend, if nobody can do it befor.
Cheers
2017-10-24 7:17 GMT+02:00, Abdel <abdelkrim.bensaid@...>:
Hi Noelia,
Thanks.
I agree.
For the instructions of use of the Appveyor service, for those who start, I think it would be also interesting to add a small explanation in the Wiki, as well as on the obtaining of a personal token for the use of the Github API.
A link to the Github help page for example.
Otherwise, the version of Python used in the appveyor.yml file is 2.7 32 bits, but it is not really useful to adapt it for Python 3, since the goal is just to build the add-on.
Cheers, Abdel.
Le 23/10/2017 à 22:16, Noelia Ruiz a écrit :
Hi:
I've seen that several authors have included an appveyor.yml file in their repos. Personally, I failed to do this until I found Abdels configuration file. I use it for several add-ons and it's comfortable for me when posting releases. Should we upload it to the nvdaaddons organization, like Addons Wizzard, Potluck or Addon Template? It could be just a gist instead of a full repo. If so, I will do it during this week, if Abdel agrees and people is interested. Comments are appreciated
Cheers
|
|
Hi, also thanks Tuukka, who include an appveyor.yml file in the reviewCursorCopier add-on. As the --egg flag is deprecated, I found this and modified slightly your appveyor.yml file to install scons: https://github.com/anholt/mesa/blob/master/appveyor.ymlI think we should include these two pages in references, and a section with aknowledgements to Derek, Tuukka and you (Abdel). I will do it later or tomorrow. Cheers I
toggle quoted message
Show quoted text
El 27/10/2017 a las 7:20, Abdel escribió: Hi Noelia, Thank you very much. I just read the page, I think it describes well the concept of using the Appveyor tool in creating and updating add-on. Thanks to Derek for being the first person to tell us about this fabulous tool on the nvda-addons mailing list. When using the appveyor.yml example provided in Derek's nvda-notepadPlusPlus repository, I could not upload the add-on to Github after build. That's why I inquired about the Appveyor forum and got the following answer: http://help.appveyor.com/discussions/questions/9221-syntax-of-the-release-name-value-in-the-deploy-section-of-the-appveyoryml-configuration-file Cheers, Abdel. Le 26/10/2017 à 22:02, Noelia Ruiz a écrit :
Hi Abdel and everyone, please review this and provide feed-back or request changes if needed:
https://github.com/nvdaaddons/nvdaaddons.github.io/wiki/appveyor
Thanks
El 24/10/2017 a las 11:21, Noelia Ruiz escribió:
Sure. We can provide an explanation too. I think that Derek was the first person on the add-ons list to suggest this, and at start I was reluctant to use it, since I thought that it wouldn't provide too much benefit, but especially if we mantain various add-ons, even from different computers, where we perhaps don't have the necessary dependencies installed, is really useful. I will upload the appveyor file with the explanation when I can, perhaps the next weekend, if nobody can do it befor.
Cheers
2017-10-24 7:17 GMT+02:00, Abdel <abdelkrim.bensaid@...>:
Hi Noelia,
Thanks.
I agree.
For the instructions of use of the Appveyor service, for those who start, I think it would be also interesting to add a small explanation in the Wiki, as well as on the obtaining of a personal token for the use of the Github API.
A link to the Github help page for example.
Otherwise, the version of Python used in the appveyor.yml file is 2.7 32 bits, but it is not really useful to adapt it for Python 3, since the goal is just to build the add-on.
Cheers, Abdel.
Le 23/10/2017 à 22:16, Noelia Ruiz a écrit :
Hi:
I've seen that several authors have included an appveyor.yml file in their repos. Personally, I failed to do this until I found Abdels configuration file. I use it for several add-ons and it's comfortable for me when posting releases. Should we upload it to the nvdaaddons organization, like Addons Wizzard, Potluck or Addon Template? It could be just a gist instead of a full repo. If so, I will do it during this week, if Abdel agrees and people is interested. Comments are appreciated
Cheers
|
|
Hi Noelia,
Thanks.
You're right, the --egg option is deprecated, it was used in the Tuukka and Derek examples too.
In the example of Tuukka, there is another mistake.
He uses the branch section and the appveyor_repo_tag environment variable that are incompatible with each other.
We can use either one or the other, but not both at the same time.
Cheers, Abdel.
toggle quoted message
Show quoted text
Le 27/10/2017 à 07:53, Noelia Ruiz a écrit : Hi, also thanks Tuukka, who include an appveyor.yml file in the reviewCursorCopier add-on. As the --egg flag is deprecated, I found this and modified slightly your appveyor.yml file to install scons:
https://github.com/anholt/mesa/blob/master/appveyor.yml
I think we should include these two pages in references, and a section with aknowledgements to Derek, Tuukka and you (Abdel).
I will do it later or tomorrow.
Cheers
I
El 27/10/2017 a las 7:20, Abdel escribió:
Hi Noelia,
Thank you very much.
I just read the page, I think it describes well the concept of using the Appveyor tool in creating and updating add-on.
Thanks to Derek for being the first person to tell us about this fabulous tool on the nvda-addons mailing list.
When using the appveyor.yml example provided in Derek's nvda-notepadPlusPlus repository, I could not upload the add-on to Github after build.
That's why I inquired about the Appveyor forum and got the following answer:
http://help.appveyor.com/discussions/questions/9221-syntax-of-the-release-name-value-in-the-deploy-section-of-the-appveyoryml-configuration-file
Cheers, Abdel.
Le 26/10/2017 à 22:02, Noelia Ruiz a écrit :
Hi Abdel and everyone, please review this and provide feed-back or request changes if needed:
https://github.com/nvdaaddons/nvdaaddons.github.io/wiki/appveyor
Thanks
El 24/10/2017 a las 11:21, Noelia Ruiz escribió:
Sure. We can provide an explanation too. I think that Derek was the first person on the add-ons list to suggest this, and at start I was reluctant to use it, since I thought that it wouldn't provide too much benefit, but especially if we mantain various add-ons, even from different computers, where we perhaps don't have the necessary dependencies installed, is really useful. I will upload the appveyor file with the explanation when I can, perhaps the next weekend, if nobody can do it befor.
Cheers
2017-10-24 7:17 GMT+02:00, Abdel <abdelkrim.bensaid@...>:
Hi Noelia,
Thanks.
I agree.
For the instructions of use of the Appveyor service, for those who start, I think it would be also interesting to add a small explanation in the Wiki, as well as on the obtaining of a personal token for the use of the Github API.
A link to the Github help page for example.
Otherwise, the version of Python used in the appveyor.yml file is 2.7 32 bits, but it is not really useful to adapt it for Python 3, since the goal is just to build the add-on.
Cheers, Abdel.
Le 23/10/2017 à 22:16, Noelia Ruiz a écrit :
Hi:
I've seen that several authors have included an appveyor.yml file in their repos. Personally, I failed to do this until I found Abdels configuration file. I use it for several add-ons and it's comfortable for me when posting releases. Should we upload it to the nvdaaddons organization, like Addons Wizzard, Potluck or Addon Template? It could be just a gist instead of a full repo. If so, I will do it during this week, if Abdel agrees and people is interested. Comments are appreciated
Cheers
|
|
toggle quoted message
Show quoted text
El 27/10/2017 a las 8:22, Abdel escribió: Hi Noelia, Thanks. You're right, the --egg option is deprecated, it was used in the Tuukka and Derek examples too. In the example of Tuukka, there is another mistake. He uses the branch section and the appveyor_repo_tag environment variable that are incompatible with each other. We can use either one or the other, but not both at the same time. Cheers, Abdel. Le 27/10/2017 à 07:53, Noelia Ruiz a écrit :
Hi, also thanks Tuukka, who include an appveyor.yml file in the reviewCursorCopier add-on. As the --egg flag is deprecated, I found this and modified slightly your appveyor.yml file to install scons:
https://github.com/anholt/mesa/blob/master/appveyor.yml
I think we should include these two pages in references, and a section with aknowledgements to Derek, Tuukka and you (Abdel).
I will do it later or tomorrow.
Cheers
I
El 27/10/2017 a las 7:20, Abdel escribió:
Hi Noelia,
Thank you very much.
I just read the page, I think it describes well the concept of using the Appveyor tool in creating and updating add-on.
Thanks to Derek for being the first person to tell us about this fabulous tool on the nvda-addons mailing list.
When using the appveyor.yml example provided in Derek's nvda-notepadPlusPlus repository, I could not upload the add-on to Github after build.
That's why I inquired about the Appveyor forum and got the following answer:
http://help.appveyor.com/discussions/questions/9221-syntax-of-the-release-name-value-in-the-deploy-section-of-the-appveyoryml-configuration-file
Cheers, Abdel.
Le 26/10/2017 à 22:02, Noelia Ruiz a écrit :
Hi Abdel and everyone, please review this and provide feed-back or request changes if needed:
https://github.com/nvdaaddons/nvdaaddons.github.io/wiki/appveyor
Thanks
El 24/10/2017 a las 11:21, Noelia Ruiz escribió:
Sure. We can provide an explanation too. I think that Derek was the first person on the add-ons list to suggest this, and at start I was reluctant to use it, since I thought that it wouldn't provide too much benefit, but especially if we mantain various add-ons, even from different computers, where we perhaps don't have the necessary dependencies installed, is really useful. I will upload the appveyor file with the explanation when I can, perhaps the next weekend, if nobody can do it befor.
Cheers
2017-10-24 7:17 GMT+02:00, Abdel <abdelkrim.bensaid@...>:
Hi Noelia,
Thanks.
I agree.
For the instructions of use of the Appveyor service, for those who start, I think it would be also interesting to add a small explanation in the Wiki, as well as on the obtaining of a personal token for the use of the Github API.
A link to the Github help page for example.
Otherwise, the version of Python used in the appveyor.yml file is 2.7 32 bits, but it is not really useful to adapt it for Python 3, since the goal is just to build the add-on.
Cheers, Abdel.
Le 23/10/2017 à 22:16, Noelia Ruiz a écrit :
Hi:
I've seen that several authors have included an appveyor.yml file in their repos. Personally, I failed to do this until I found Abdels configuration file. I use it for several add-ons and it's comfortable for me when posting releases. Should we upload it to the nvdaaddons organization, like Addons Wizzard, Potluck or Addon Template? It could be just a gist instead of a full repo. If so, I will do it during this week, if Abdel agrees and people is interested. Comments are appreciated
Cheers
|
|
Interesting. I looked for something like that for quite some time.
toggle quoted message
Show quoted text
On Thu, Oct 26, 2017 at 11:53 PM, Noelia Ruiz <nrm1977@...> wrote: Hi, also thanks Tuukka, who include an appveyor.yml file in the reviewCursorCopier add-on.
As the --egg flag is deprecated, I found this and modified slightly your appveyor.yml file to install scons:
https://github.com/anholt/mesa/blob/master/appveyor.yml
I think we should include these two pages in references, and a section with aknowledgements to Derek, Tuukka and you (Abdel).
I will do it later or tomorrow.
Cheers
I
El 27/10/2017 a las 7:20, Abdel escribió:
Hi Noelia,
Thank you very much.
I just read the page, I think it describes well the concept of using the Appveyor tool in creating and updating add-on.
Thanks to Derek for being the first person to tell us about this fabulous tool on the nvda-addons mailing list.
When using the appveyor.yml example provided in Derek's nvda-notepadPlusPlus repository, I could not upload the add-on to Github after build.
That's why I inquired about the Appveyor forum and got the following answer:
http://help.appveyor.com/discussions/questions/9221-syntax-of-the-release-name-value-in-the-deploy-section-of-the-appveyoryml-configuration-file
Cheers,
Abdel.
Le 26/10/2017 à 22:02, Noelia Ruiz a écrit :
Hi Abdel and everyone, please review this and provide feed-back or request changes if needed:
https://github.com/nvdaaddons/nvdaaddons.github.io/wiki/appveyor
Thanks
El 24/10/2017 a las 11:21, Noelia Ruiz escribió:
Sure. We can provide an explanation too.
I think that Derek was the first person on the add-ons list to suggest
this, and at start I was reluctant to use it, since I thought that it
wouldn't provide too much benefit, but especially if we mantain
various add-ons, even from different computers, where we perhaps don't
have the necessary dependencies installed, is really useful.
I will upload the appveyor file with the explanation when I can,
perhaps the next weekend, if nobody can do it befor.
Cheers
2017-10-24 7:17 GMT+02:00, Abdel <abdelkrim.bensaid@...>:
Hi Noelia,
Thanks.
I agree.
For the instructions of use of the Appveyor service, for those who
start, I think it would be also interesting to add a small explanation
in the Wiki, as well as on the obtaining of a personal token for the use
of the Github API.
A link to the Github help page for example.
Otherwise, the version of Python used in the appveyor.yml file is 2.7 32
bits, but it is not really useful to adapt it for Python 3, since the
goal is just to build the add-on.
Cheers,
Abdel.
Le 23/10/2017 à 22:16, Noelia Ruiz a écrit :
Hi:
I've seen that several authors have included an appveyor.yml file in
their repos. Personally, I failed to do this until I found Abdels
configuration file. I use it for several add-ons and it's comfortable
for me when posting releases.
Should we upload it to the nvdaaddons organization, like Addons
Wizzard, Potluck or Addon Template?
It could be just a gist instead of a full repo. If so, I will do it
during this week, if Abdel agrees and people is interested.
Comments are appreciated
Cheers
-- Derek Riemer: Improving the world one byte at a time!
- University of Colorado Boulder Department of computer science, 4th year undergraduate student.
- Accessibility enthusiast.
- Proud user of the NVDA screen reader.
- Open source enthusiast.
- Skier.
Personal website
|
|
Wait, how come? Doesn't branch take on the name of the tag if it's a tag?
toggle quoted message
Show quoted text
On Fri, Oct 27, 2017 at 12:22 AM, Abdel <abdelkrim.bensaid@...> wrote: Hi Noelia,
Thanks.
You're right, the --egg option is deprecated, it was used in the Tuukka and Derek examples too.
In the example of Tuukka, there is another mistake.
He uses the branch section and the appveyor_repo_tag environment variable that are incompatible with each other.
We can use either one or the other, but not both at the same time.
Cheers,
Abdel.
Le 27/10/2017 à 07:53, Noelia Ruiz a écrit :
Hi, also thanks Tuukka, who include an appveyor.yml file in the reviewCursorCopier add-on.
As the --egg flag is deprecated, I found this and modified slightly your appveyor.yml file to install scons:
https://github.com/anholt/mesa/blob/master/appveyor.yml
I think we should include these two pages in references, and a section with aknowledgements to Derek, Tuukka and you (Abdel).
I will do it later or tomorrow.
Cheers
I
El 27/10/2017 a las 7:20, Abdel escribió:
Hi Noelia,
Thank you very much.
I just read the page, I think it describes well the concept of using the Appveyor tool in creating and updating add-on.
Thanks to Derek for being the first person to tell us about this fabulous tool on the nvda-addons mailing list.
When using the appveyor.yml example provided in Derek's nvda-notepadPlusPlus repository, I could not upload the add-on to Github after build.
That's why I inquired about the Appveyor forum and got the following answer:
http://help.appveyor.com/discussions/questions/9221-syntax-of-the-release-name-value-in-the-deploy-section-of-the-appveyoryml-configuration-file
Cheers,
Abdel.
Le 26/10/2017 à 22:02, Noelia Ruiz a écrit :
Hi Abdel and everyone, please review this and provide feed-back or request changes if needed:
https://github.com/nvdaaddons/nvdaaddons.github.io/wiki/appveyor
Thanks
El 24/10/2017 a las 11:21, Noelia Ruiz escribió:
Sure. We can provide an explanation too.
I think that Derek was the first person on the add-ons list to suggest
this, and at start I was reluctant to use it, since I thought that it
wouldn't provide too much benefit, but especially if we mantain
various add-ons, even from different computers, where we perhaps don't
have the necessary dependencies installed, is really useful.
I will upload the appveyor file with the explanation when I can,
perhaps the next weekend, if nobody can do it befor.
Cheers
2017-10-24 7:17 GMT+02:00, Abdel <abdelkrim.bensaid@...>:
Hi Noelia,
Thanks.
I agree.
For the instructions of use of the Appveyor service, for those who
start, I think it would be also interesting to add a small explanation
in the Wiki, as well as on the obtaining of a personal token for the use
of the Github API.
A link to the Github help page for example.
Otherwise, the version of Python used in the appveyor.yml file is 2.7 32
bits, but it is not really useful to adapt it for Python 3, since the
goal is just to build the add-on.
Cheers,
Abdel.
Le 23/10/2017 à 22:16, Noelia Ruiz a écrit :
Hi:
I've seen that several authors have included an appveyor.yml file in
their repos. Personally, I failed to do this until I found Abdels
configuration file. I use it for several add-ons and it's comfortable
for me when posting releases.
Should we upload it to the nvdaaddons organization, like Addons
Wizzard, Potluck or Addon Template?
It could be just a gist instead of a full repo. If so, I will do it
during this week, if Abdel agrees and people is interested.
Comments are appreciated
Cheers
-- Derek Riemer: Improving the world one byte at a time!
- University of Colorado Boulder Department of computer science, 4th year undergraduate student.
- Accessibility enthusiast.
- Proud user of the NVDA screen reader.
- Open source enthusiast.
- Skier.
Personal website
|
|
Hi Derek,
Interesting question.
In fact, according to this article
in the Appveyor documentation, the branch section and the tag are
mutually exclusive.
We can use either one or the other, but not both at the same time.
If we want to have them in the same configuration file, we have to
put a condition.
In the example of Tuukka, he put both of them unconditionally.
Here is the paragraph that talks about this in the documentation:
However please note that branch and
appveyor_repo_tag are mutually exclusive. This is because in
case of tag, it replaces branch in webhook content and there are
no practically reliable way to recognize from what branch tag
was created. Therefore with this setting deployment will happen
only for master branch:
- provider: Environment
name: production
on:
branch: master # only this will work
appveyor_repo_tag: true # condition will never be evaluated
So if you need to deploy on both branch and tag, please create
two provider sections under deploy like this:
deploy:
- provider: Environment
name: production
on:
branch: master
- provider: Environment
name: production
on:
appveyor_repo_tag: true
skip_tags: true
Thanks.
Cheers,
Abdel.
Le 28/10/2017 à 01:58, derek riemer a
écrit :
Wait, how come? Doesn't branch take on the name of
the tag if it's a tag?
|
|
Actually, I wrote that code, we coauthored the notepad-++ addon together. Yeah, that's a problem.
toggle quoted message
Show quoted text
On Sat, Oct 28, 2017 at 12:13 AM, Abdel <abdelkrim.bensaid@...> wrote:
Hi Derek,
Interesting question.
In fact, according to this article
in the Appveyor documentation, the branch section and the tag are
mutually exclusive.
We can use either one or the other, but not both at the same time.
If we want to have them in the same configuration file, we have to
put a condition.
In the example of Tuukka, he put both of them unconditionally.
Here is the paragraph that talks about this in the documentation:
However please note that branch and
appveyor_repo_tag are mutually exclusive. This is because in
case of tag, it replaces branch in webhook content and there are
no practically reliable way to recognize from what branch tag
was created. Therefore with this setting deployment will happen
only for master branch:
- provider: Environment
name: production
on:
branch: master # only this will work
appveyor_repo_tag: true # condition will never be evaluated
So if you need to deploy on both branch and tag, please create
two provider sections under deploy like this:
deploy:
- provider: Environment
name: production
on:
branch: master
- provider: Environment
name: production
on:
appveyor_repo_tag: true
skip_tags: true
Thanks.
Cheers,
Abdel.
Le 28/10/2017 à 01:58, derek riemer a
écrit :
Wait, how come? Doesn't branch take on the name of
the tag if it's a tag?
-- Derek Riemer: Improving the world one byte at a time!
- University of Colorado Boulder Department of computer science, 4th year undergraduate student.
- Accessibility enthusiast.
- Proud user of the NVDA screen reader.
- Open source enthusiast.
- Skier.
Personal website
|
|
However, it says that "branchh replaces tag in the github webhook" so that's why my code works. I can use the branch variable I am pretty sure.
toggle quoted message
Show quoted text
On Sun, Oct 29, 2017 at 11:03 PM, Derek Riemer <driemer.riemer@...> wrote: Actually, I wrote that code, we coauthored the notepad-++ addon together. Yeah, that's a problem.
-- Derek Riemer: Improving the world one byte at a time!
- University of Colorado Boulder Department of computer science, 4th year undergraduate student.
- Accessibility enthusiast.
- Proud user of the NVDA screen reader.
- Open source enthusiast.
- Skier.
Personal website
|
|