Open RandomDSdevel opened 7 years ago
Or I could just go and add you to the ACL for the repo 😛
@dshadowwolf: Well, yes, you could do that, but do you really think I deserve such an honor at this point in time? I mean, I'm barely just starting to actually learning to put what little I know about one programming language in particular into practice by going through/over a textbook on it again, but this time actually doing the exercises in it. If that's enough for you, then I might consider accepting your invitation, but the prospect is, still, somewhat daunting at this point in my (still mostly informal) education.
@dshadowwolf: Or do you think I'm just being silly by balking like this?
I'm offering you full access and all that entails so you can do what you'd like and you're balking at it. I have to admire the humility, but at this point I've talked with you enough to have some trust and think you're ready for a bit more responsibility.
After all, when I flip this to a community/github org, I'm thinking of naming you my second or third :)
Whoa/wow, thanks! I don't know if I deserve that high of a rank since I'll probably be doing other stuff in the near future, but cool! Guess I'll go ahead and click that button, then! (Wanders off to do so…)
Huh, push access doesn't let me edit the repository description (which is why I suggested adding a .github/config.yml
, so I could push changes to it, though that doesn't have to happen if you're not comfortable with it.) To wit, the text in question currently reads 'Ideas for a modern cross-paradigm programming language' (sic,) but there should be an 'e' on the end of that (and a period and two spaces if you intend for it to look like a full sentence even though it isn't one.) I'll go ahead and fix it on my fork — speaking of said fork, should I keep it around even though I now have push access (y'know, for the niceties of the protocol recommended in the form of the GitHub flow…)
heh, funny, never noticed that
Fixed :)
Cool, and I've updated my fork's description to match.
…except that, having push access, now I can edit your issue comments as if GitHub thinks I'm you to some extent, too, strange as that is. Darn it, I've come across this problem before…; ah, well, it's not like I'm that nefarious, right? 😉 (JK about the wink.)
@dshadowwolf: Closing #11 should resolve this last peculiarity here, I think?
@dshadowwolf: On a note more related to this issue's original focus, you messed up the Markdown header syntax on your README with a recent commit. Should I open a new issue for that?
@dshadowwolf: You've got a typo in this repository's description (displayed as a subtitle on its main code-browsing page.) Could you set up Probot's Settings app/daemon (né Configurer) for this Repository so I could submit a PR modifying the resulting
.github/config.yml
to fix it for you?