Kind replies

 Reply

Yup, agreed. I guess it depends too on the bottom line and what a cost implication it has, as well as maybe not being as "good" a referral if it's not as close to real word of mouth?

This is also the way my company changed our referral scheme and it makes it a bit more awkward because you have to actively ask for someone's details to refer them, whereas before you got it through folks following the link, which feels less invasive to me

 Reply

Yeah that's what I'm thinking. It's a shame cause some services I'd happily add an affiliate link when talking about them if I believed in them, but I can see why they may want to do that

 Reply

I wonder if doing it via email is making it an actual referral rather than just allowing someone to search for the code, so it's more the intent than a limitation?

 Reply

I want to say they're not available via API as I can't see them in https://granary.io which I use for rendering context on my site

 Reply

I've got ~/workspaces which is maybe a repo or maybe a group of projects ie "hacktoberfest/2020". At work, a git clone from our internal GitHub goes to ~/workspaces/$org/$repo as that makes it much easier to navigate

 Reply

When I interact with Twitter from my website I store a copy of the original post (to provide context on my site) but that helps me capture this for longer-term usage, and I've been able to go back through now deleted tweets!

 Reply

As long as you have consent of all authors you can change license at any point then yeah you can, although a commit with a prior licence will still abide by that license, ie allowing folks to continue using software after it's made proprietary etc

 Reply

Ah crap Steve really sorry to hear that - stay safe and let us know if we can do anything to help πŸ€—

 Reply

https://docs.github.com/en/free-pro-team@latest/github/site-policy/github-terms-of-service#5-license-grant-to-other-users notes that it's just making a copy ie GitHub's fork button, not then making changes on top of it

 Reply

"view and fork" != being able to make modifications, so I think my point still stands - I'll have a read of the terms of service though to refresh my understanding though thanks!

 Reply

If your portfolio doesn't have a license on it, it's technically illegal for them to contribute to it because it defaults to proprietary. Not many folks realise that, so contributions may come in. But yep, folks raising PRs is possible if a repo is public and they want to help / etc

 Reply

I've just upgraded from slimline to full size and being able to wash plates is amazing, I can't imagine the joy of going from nothing to dishwasher!

 Reply

I'm sure I've seen this when you look at the merge commit, or commits on the main branch, if the repo uses tagging - it shows all tags applicable, so you have to do some thinking to find the first

 Reply

It's also possible to be able to do i.e. git checkout origin/pull/1/head via https://www.jvt.me/posts/2019/01/19/git-ref-github-pull-requests/

 Reply

Supportability / operability is a big one for me - both, "what will the next team supporting this project think of this code" and "am I going to be annoyed if I get called out for this unnecessary ERROR log"? Also being much more considered for writing code that is (hopefully) more understandable than idiomatic, as folks don't necessarily come to the job with strong language knowledge, and making things understandable by all is better than a subset who know the language better