Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Jan 19 13:25
    LordMike opened #728
  • Jan 18 21:27
    AdmiringWorm commented #727
  • Jan 18 21:12
    egreiner opened #727
  • Jan 17 08:54
    nutterthanos edited #722
  • Jan 14 12:02
    dancingdoorman opened #726
  • Jan 10 14:38
    PowerPCx86 opened #725
  • Jan 07 09:13
    gep13 commented #724
  • Jan 07 09:12

    gep13 on develop

    (GH-711) prelease label should … (GH-711) prelease label should … (compare)

  • Jan 07 09:12
    gep13 closed #724
  • Jan 07 09:12
    gep13 closed #711
  • Jan 06 21:00
    mkevenaar edited #724
  • Jan 06 20:58
    mkevenaar edited #724
  • Jan 06 20:57
    mkevenaar opened #724
  • Jan 05 10:44
    jmacura edited #723
  • Jan 03 15:59
    gep13 commented #723
  • Jan 03 14:04
    jmacura commented #723
  • Jan 03 13:57
    gep13 closed #723
  • Jan 03 13:57
    gep13 labeled #723
  • Jan 03 13:57
    gep13 commented #723
  • Jan 03 13:26
    jmacura opened #723
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?
I have rebased your branch, and force pushed onto it
Manfred Wallner
@mwallner
:D thanks
Gary Ewan Park
@gep13
if you want to grab the latest, you would need to delete your local version of it git branch -D issue/331
and then do git fetch
Richard Simpson
@RichiCoder1
Yup.
Manfred Wallner
@mwallner
yup, all there .. silly to have 3 persons struggle with git for a one-liner ^^
Gary Ewan Park
@gep13
git checkout issue/331
and you should be back in line
i.e. if you wanted more changes to be done etc
there is also a git reset command that you could use, but I prefer deleting and re-fetching
Richard Simpson
@RichiCoder1
Random: @/all would the preference for Gui to be that it always starts as Admin, or that it starts as User, and then elevates as need?
I ask because the latter would require elevating (aka spinning up a new gui) the first time you wanted to install/uninstall/pin/etc... which might get irritating. Possibly thinking about adding a run as admin shortcut for chocolatey gui, but that might also be complicated. shrug
Gary Ewan Park
@gep13
@mwallner the fact that I can now do what I just did, on your repo, without needing to be a collaborator on it, it a HUGE step forward though
means we can step in, if/when required
rather than having you struggle with it, when you are just ramping up on git
@RichiCoder1 I would suggest prompting on startup
@scottisafool might think otherwise though :-)
Manfred Wallner
@mwallner
@RichiCoder1 elevate once on startup .. anything else might be annoying :-)
Richard Simpson
@RichiCoder1
Hmm. Sort of a "first run", "Would you like to run as admin?" kind of thing? Throw in a Don't ask again check box, and it might not be overly user hostile.
Mordechai Zuber
@M-Zuber
👆👆👆👆
Richard Simpson
@RichiCoder1
@M-Zuber Was that a yes to me or @mwallner ?
Mordechai Zuber
@M-Zuber
To you, although the two of you seems to be saying pretty much the same thing