#16050 Recommended workflows for working with private artifacts Issue created by davidreuss Currently it is reasonably easy to download artifacts from public endpoints. But there does not seem to be standard support for pulling in github repositories (public or private), or artifacts. Describe the solution you'd like Many projects have github artifacts published as assets onto a release. It would be great if it was straight forward to consume artifacts/assets from a release and make available to other pants goal/target. Standardised/recommended workflows regarding how to deal with secrets/tokens would be appreciated. Specifically on consuming github release artifacts, which usually is a two step/request process, where you first need to identify the release, and then subsequently pull down the assets. How does it become easy to configure while pants makes fingerprinting/checksumming easy for the end-user? Describe alternatives you've considered Writing custom plugins to source from various repositories, hardcoding necessary secrets within the plugins. Does not seem desirable 😄 Additional context • Original slack thread re. feature support pantsbuild/pants