Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Dec 04 18:14
    mtnielsen commented #718
  • Dec 04 18:13
    mtnielsen closed #718
  • Dec 04 18:13
    mtnielsen commented #718
  • Dec 04 16:42
    gep13 commented #718
  • Dec 04 14:54
    mtnielsen commented #718
  • Dec 04 14:53
    mtnielsen commented #718
  • Dec 04 14:53
    mtnielsen commented #718
  • Dec 04 14:52
    mtnielsen commented #718
  • Dec 04 14:16
    gep13 commented #718
  • Dec 04 14:04
    mtnielsen opened #718
  • Nov 25 21:20
    gep13 commented #717
  • Nov 25 21:20

    gep13 on develop

    GH-716 use chocolateyguicli ins… use chocolateyguicli instead of… (compare)

  • Nov 25 21:19
    gep13 closed #717
  • Nov 25 21:19
    gep13 closed #716
  • Nov 25 21:12
    gep13 milestoned #716
  • Nov 25 21:12
    gep13 labeled #716
  • Nov 25 19:20
    mwallner review_requested #717
  • Nov 25 19:20
    mwallner opened #717
  • Nov 25 19:20
    mwallner assigned #717
  • Nov 25 19:14
    mwallner assigned #716
Manfred Wallner
@mwallner
@dragon788 ++ :D
Gary Ewan Park
@gep13
@dragon788 I code all day in C#, so writing my build scripts in it as well is a welcome relief to having to code in something else, especially when things aren't working. The ability to debug the build scripts as well is very useful :-D
Richard Simpson
@RichiCoder1
Agreed.
Gary Ewan Park
@gep13
bear in mind, I am slightly biased, as I am one of the maintainers of the cake project :-D
and @RichiCoder1 is a long time contributor to it
Richard Simpson
@RichiCoder1
Yup. So just a liiiitle bias there.
Gary Ewan Park
@gep13
but yeah, you should TOTALLY use it :-P
dragon788
@dragon788
yeah, I've been playing with PowerShell most of the time these days so same language = winning
Richard Simpson
@RichiCoder1
Gonna do a little more work to make Gui more error resilent (or at least have it tell you something went wrong), but I think that'll be about it pending a better UI from choco.
Gary Ewan Park
@gep13
:+1:
Richard Simpson
@RichiCoder1
After that I think I'm actually quite happy with the current state of Gui. Just need to start tackling the backlog of QoL improvments I've been putting off.
The chocolatiest bot this side of the Mississippi
@choco-bot
Richard Simpson
@RichiCoder1
^ exactly.
Gary Ewan Park
@gep13
sounds good! Been a long time since a release, so it will be great to get this one out the door!
Richard Simpson
@RichiCoder1
Aaaaamen. Especially since i think 50% of the recent issues is just the poor souls suffering from the poor choco interop in the previous version
Gary Ewan Park
@gep13
When we do a release, can we keep this in mind :point_up: https://gitter.im/chocolatey/ChocolateyGUI?at=583f003489d179bf4de4c8ee
exactly
Richard Simpson
@RichiCoder1
I'd be fine skipping to 0.15
Holding off on 1.x until we have a better choco API.
Gary Ewan Park
@gep13
yip, that makes sense to me
Richard Simpson
@RichiCoder1
One Framework Overhaul is merged and I knock out a few more QoL issues, I definitely also want to do a 0.15 RC so we can get some feedback from people and make sure I'm not missing anything. Not planning to make this the end-all-be-all release, but I would like this to be as polished as possible.
Gary Ewan Park
@gep13
makes sense to me
Manfred Wallner
@mwallner
:+1:
Gary Ewan Park
@gep13
@mwallner we will assume that the beers are in the post :-D
Manfred Wallner
@mwallner
:D I'll der to it ;-)
(I'll see .. stupid Android Gitter Client...)
Gary Ewan Park
@gep13
good man! :-D
Richard Simpson
@RichiCoder1
Aaaaaand framework overhaul is now in develop.
Gary Ewan Park
@gep13
woo hoo!
Manfred Wallner
@mwallner
yieha!
concerning chocolatey/ChocolateyGUI#335 - afaik it just needs to be hotfixed in another/new file as the file structure/names have changed a little? .. haven't got a Win PC in reach tonight - will do it asap tomorrow morning
Richard Simpson
@RichiCoder1
Yup. The file honestly didn't change much, git is just being picky
Manfred Wallner
@mwallner
@RichiCoder1 just fixed in current upstream/develop and created a pull request.. anyway there seems something odd, now I've got a commit from you as well in the PR .. (sorry - just starting to contribute via git/github/PRs .. normally a accurev guy :worried: )
Gary Ewan Park
@gep13
@mwallner sounds like you need a rebase. What approach did you take to update the PR?
@mwallner ^^
Manfred Wallner
@mwallner
darn .. didn't do the rebase thing .. just pulled from new upstream
Gary Ewan Park
@gep13
that would do it :-D
never pull, always rebase :-D
:-D
Manfred Wallner
@mwallner
do you think chocolatey/ChocolateyGUI#345 can be merged or do I have to the rebase and create another PR ?
:D
Gary Ewan Park
@gep13
creating a new PR is almost never needed. Give me a minute...
do you have any changes in your local cloned branch that you wouldn't want to lose?
Manfred Wallner
@mwallner
hm .. lemme check
well, no, as @RichiCoder1 already merged feature_overhaul - that's basically what I did - so a 'clean' upstream/devel + the PR is all I need
Richard Simpson
@RichiCoder1
Darn't git. Y u complicated?
Gary Ewan Park
@gep13
does that cover it?