Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Aug 22 13:22
    Sukender opened #694
  • Aug 21 06:41
    gep13 closed #693
  • Aug 21 06:41
    gep13 commented #693
  • Aug 21 06:40
    gep13 milestoned #693
  • Aug 21 06:40
    gep13 labeled #693
  • Aug 21 06:40

    gep13 on develop

    (GH-693) Clarify usage requirem… (compare)

  • Aug 21 06:39

    gep13 on develop

    (maint) Remove mention of ZenHu… (compare)

  • Aug 21 04:00
    Lemmingh opened #693
  • Aug 09 14:39
    cybercatgurrl commented #617
  • Aug 01 08:39
    pascalberger commented #692
  • Aug 01 07:56
    gep13 commented #692
  • Aug 01 07:34

    mwallner on develop

    (build) Disable documentation o… (compare)

  • Aug 01 07:34
    mwallner closed #692
  • Aug 01 07:33

    mwallner on develop

    (doc) Fix typo (#691) (compare)

  • Aug 01 07:33
    mwallner closed #691
  • Jul 31 05:46
    AdmiringWorm commented #637
  • Jul 30 21:36
    pascalberger opened #692
  • Jul 30 21:32
    pascalberger opened #691
  • Jul 30 19:41
    mwallner commented #637
  • Jul 28 13:02
    pherwanikar commented #12
Sander Steenhuis
@Redsandro
@gep13 thanks for the clarification :)
@gep13 Yeah the highlight/@mention was more general advice in case it was a 'feature' that a bot would always mention the chan. I could have known better if I saw what was going on here. :) Not really used to coming here and staying uptodate. You can keep me in the group. :)
clap
Sander Steenhuis
@Redsandro
chocobot clap
I have no power here.
Gary Ewan Park
@gep13
ah, hold on, if you are new to Gitter, or at least reasonably new, we need to kick chocobot so that he/she can see you, two secs...
chocobot uptime
The chocolatiest bot this side of the Mississippi
@choco-bot
I've been sentient for 22 hours, 57 minutes and 47 seconds
Gary Ewan Park
@gep13
chocobot uptime
The chocolatiest bot this side of the Mississippi
@choco-bot
I've been sentient for 4 seconds
Gary Ewan Park
@gep13
@Redsandro can you try talking to chocobot again?
cool, I will keep you in the group
let me know if you have any other questions
chocobot clap
slow clap
Sander Steenhuis
@Redsandro
clap
sarcastic applause
The chocolatiest bot this side of the Mississippi
@choco-bot
Sander Steenhuis
@Redsandro
ah :D
Gary Ewan Park
@gep13
woot!
choobot botsnack
The chocolatiest bot this side of the Mississippi
@choco-bot
Thank you very much.
Gary Ewan Park
@gep13
good chocobot!
Sander Steenhuis
@Redsandro
chocobot translate me from javascript into java var test = { key: "value"};
The chocolatiest bot this side of the Mississippi
@choco-bot
" from javascript into java var test = { key: "value"};" is English for " from javascript into java var test = { key: "value"};"
Simon Cropp
@SimonCropp
@gep13 shall we move here instead of twitter DMs ?
Gary Ewan Park
@gep13
that is probably a good idea :-)
so, this is what I have....
ChocolateyGUI has both a develop and a master branch, we are following GitFlow
we are using GitVersion and the built in support for AppVeyor to generate the version number each time a build occurs
I have the building of the branches set up as follows...
if on develop branch, and it is a pull request, run the build but no deployment
if on develop branch, and there is no pull request, run the build and deploy to MyGet Develop Feed
if on master branch, and it is a pull request, run the build, but no deployment
if on master branch, and there is no pull request, run the build and deploy to MyGet Master Feed
if on master branch, and a tag has just been applied, run the build, and deploy to Chocolatey.org
now, the last two, I could really do as one step, however, what I woudl like to introduce, is the generation of the GitHubReleaseNotes
so, the above will change to...
if on master branch, and there is no pull request, run the build, generate GitHub Release Notes, and deploy to MyGet Master Feed
assuming everything is ok, complete the draft release that was created in GitHub, thus tagging the repository which will then trigger
if on master branch, and a tag has just been applied, run the build, and deploy to Chocolatey.org
Simon Cropp
@SimonCropp
so that all sounds good
Gary Ewan Park
@gep13
this change is really the equivalent of your wait step in Octopus
does that makes sense?
The couple questions that I have would be as follows...
technically, when creating the release notes, I could also upload the assets, i.e. the nupkg and msi, however, these won't be the "exact" same files taht are sent to chocolatey.org. Now, granted they will be the exact same, as the source code could/should be exactly the same, the only difference is that a tag has been applied, however, to make things straight in my head, I think I want to update the now published release to include the actual assets. Do you think it would be an easy extension to GitHubReleaseNotes to allow the uploading of assets into a release? I can certainly do this through the UI, so hoping that Octokit can do it as well.
and secondly, i am currently maintaing a changelog.md file, which allows the reading of the release notes within ChocolateyGUIL
however, I don't like maintaining this information in two places, i.e. GitHub Releases, and the Changelog.md