Isuru Fernando
Isuru Fernando
Btw, I usually add these to `~/.config/git/ignore` so that it is global.
> My personal policy is to not add those and let users deal with a local non-versioned .gitignore or their own global config. Same here > However, a conda-forge feedstock...
My point is that either we should add none, or add a reasonably comprehensive list. Anything in between is worthless. > I think letting users deal with their own global...
> How about just adding just the files needed as in, https://stackoverflow.com/a/987162/4768820 ? What do you think about this? Instead of rejecting IDE files in `.gitignore`, just approve files that...
> I wouldn't be confident making that change as I don't think I've got a broad-enough view of all CF development to know what files should be whitelisted. I was...
These tokens are not sent to Pull Request builds at all. Can you ask upstream developers of sbt to provide a workaround?
There's really no way to send secrets to Pull request builds as any github user can start a PR and that would become a security issue.
> e.g. it would help me a lot on the faiss-feedstock, where the GPU lib takes between 3-5h to build, often leaving not enough time for the python bindings I...
> I just thought that splitting jobs by output might actually be easier than separating build & test phases No, it's not. While conda-build has functionaility to separate build &...
> re:implementability, but conda-build already generates a DAG of outputs and processes them in the correct order. conda-build runs the top level build.sh first and then copies the working directory...