Has anyone done research on the best place within a pull request to hide stuff?
I'm thinking it's 80% through a good sized PR. At that point the reviewer is probably tired, but you're past the end where they might scroll to and perk back up.
Has anyone done research on the best place within a pull request to hide stuff?
I'm thinking it's 80% through a good sized PR. At that point the reviewer is probably tired, but you're past the end where they might scroll to and perk back up.
@preinheimer Big changes to package-lock.json, for NodeJS apps. Big changes get hidden in GitHub's PR interface. Also, I'll assume that any changes to package-lock.json were auto-generated. Also, I have no effin idea what the syntax of that file is.
@heiglandreas @preinheimer that's too big, though. Pushing that kind of change requires a lot of trust.
@preinheimer I'd say someqhere between file 235 and 317 of that 623 File PR with 12.437 changed lines....
GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.
All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.