- Notifications
You must be signed in to change notification settings - Fork1.1k
Assignees rename fields#1076
Uh oh!
There was an error while loading.Please reload this page.
Conversation
@gjtorikian Any thoughts here? |
It's definitely clever, but I think we should just opt for explicitness.@Shredder121, would you mind simply copying the |
Should I also use the values fromhttps://api.github.com/users/hubot? |
And what about |
@Shredder121 Nah, you can keep the |
This introduces new constants, so that they can be used in otherplaces as well.This makes the data a little more realistic.
9316208
toaae43ca
CompareThere, how's that? |
What happened to Travis? |
@Shredder121 not sure but reactivated it now. |
Beautiful. Thanks as always@Shredder121! |
Haha, no problem as always! 👍 |
I saw that the original user was not in the
assignees
list, and that the users in theassignees
list weren't consistent.This updates (merges) the
USER
with itself, updating all fields with the block. (if anyone knows of a nicer way, let me know)This makes the data a little more realistic.