Closed patcon closed 5 years ago
Email sent!
Hey @jgreet! (Worth a shot, right?)
Just filed a ticket here if you would be so kind as to add it to your internal issue tracker: https://github.com/isaacs/github/issues/100
Thanks yo!
Patrick
Also, here is some daily double-bear-learning:
Bears are mammals of the family Ursidae. Bears are classified as caniforms, or doglike carnivorans, with the pinnipeds being their closest living relatives. Although only eight species of bears are extant, they are widespread, appearing in a wide variety of habitats throughout the Northern Hemisphere and partially in the Southern Hemisphere. Bears are found on the continents of North America, Central America, South America, Europe, and Asia.
Common characteristics of modern bears include large bodies with stocky legs, long snouts, shaggy hair, plantigrade paws with five nonretractile claws, and short tails. While the polar bear is mostly carnivorous and the giant panda feeds almost entirely on bamboo, the remaining six species are omnivorous, with varied diets.
Bears are mammals of the family Ursidae. Bears are classified as caniforms, or doglike carnivorans, with the pinnipeds being their closest living relatives. Although only eight species of bears are extant, they are widespread, appearing in a wide variety of habitats throughout the Northern Hemisphere and partially in the Southern Hemisphere. Bears are found on the continents of North America, Central America, South America, Europe, and Asia.
Common characteristics of modern bears include large bodies with stocky legs, long snouts, shaggy hair, plantigrade paws with five nonretractile claws, and short tails. While the polar bear is mostly carnivorous and the giant panda feeds almost entirely on bamboo, the remaining six species are omnivorous, with varied diets.
Oops. Forgot to post response:
Hey Patrick,
Sure thing, I've added assigning issues to non-collaborators to our internal feature request list.
Thanks for the feedback and the link to the original discussion.
Cheers, John
:+1:
:+1: please
Has this been added yet?
Would make life easier :+1:
I would also quite like this :+1:
I would love this :+1:
Fully agree with this request :+1:
:+1:
Definitelly would want that!
:+1:
want ! ty
:+1:
+1
+1
+1
:+1:
+1
+1
:+1:
:+1:
:+1:
:+1:
:+1:
:+1:
Any updates, I really could do with this, since I don't want to give them access to push into the repo (all collaborators are working from forks)
I'm honestly surprised this isn't a feature, and I don't see anybody even proposing a work-around. My teammates all have forks, and I can't assign anything to them without giving them push access. Can something like this be done with the paid github version?
+1
Seriously, it's been three years. Is this such a big issue?
This is a serious friction when managing popular projects with lots of contributors who volunteer to help in small ways. Has anyone found a workaround?
Yes I still have this problem, work arounds would be great
Can't they just give different access levels to collaborators? Do we really need to use an external service only because of this? 🤔
Well, the workaround is "obvious": fork, duplicate the issue in your fork and add a link to the parent repo, do all the discussion in the parent and handle state in the fork. You would still probably have to grant access to the "master" in your fork so they can coordinate.
Also, one day the Sun will engulf the Earth so this doesn't matter anyway...
Also, one day the Sun will engulf the Earth so this doesn't matter anyway.…
@Fuco1 You forgot the obligatory XKCD, so folks know what you mean! 😂:
Please add this already
Good lord, how is such a basic issue not yet implemented?
+1
+1
+1
Please stop writing new comments with +1
and :+1:, you notify dozens of other people about your wordless opinion. Put your finger up in the first comment, that's enough.
Hello all,
So I've been struggling with this myself and what I'm planning to do is to build a bot or application that:
might be risky, and you'll need to spread awareness about this in your repo but atleast can get the Job done
Hope this suggestion helps :)
+1
Sigh, I'm starting to think "internal feature list" is lingo for "ignore list."
@salameer it's done already! https://github.com/isaacs/github/issues/153#issuecomment-324964752
:)
IMO, this makes the issue tracker kind of a pain in the butt -- might as well use a dedicated issue tracker if you can't assign other people. Perhaps limit it to anyone who's done anything in the project, comments, PRs, etc
+1
👍
+1
+1
+1
Context: https://github.com/drush-ops/drush/pull/88#issuecomment-24595732
Currently, if a potential contributor want's to publicly assign themselves to a particular issue, they apparently must be granted push access to the repo. This makes it difficult for a potential contributor to "bookmark" an issue for later effort, making full use of this issue listing: https://github.com/dashboard/issues/assigned?direction=asc&sort=updated&state=open
(Alternatively, "push" access collaborators should also be able to assign issues to themselves. Specifically reticketed this is #153)
cc: @greg-1-anderson
(Sent an email to support@github.com. Will publish response here. Whoop whoop!)