Howdy folks,
I was looking at our repo on Github, and frankly, I like it. But, I know for some employers they're rating potential employees on their Github profiles (I don't agree with this, but it happens) and so not having the commits in Github reduces the exposure for that work. This probably effects our "interns" from Google SoC and Outreachy the most. For reference: https://github.com/inkscape/inkscape The problem we've had in the past is that when we had the repo on Github, people would fork it and create Pull Requests that no one would see or triage. Which would frustrate folks (understandably) and look poor on the project. The idea that I had is that we take the Inkscape repo, and we make a branch "github" that has the same README and graphic that is currently up on Github. We push the full Inkscape repo, but then set the default visible branch to the "github" branch. So anyone going to the repository sees exactly the same thing. Github doesn't seem to have a mechanism for disabling PRs, or forks. So we're relying on people actually reading the text. But I was curious what folks thought about the idea. Ted