PhilApprovalFlow
sourcelink
| PhilApprovalFlow | sourcelink | |
|---|---|---|
| 1 | 7 | |
| 2 | 1,228 | |
| - | 1.3% | |
| 5.3 | 9.0 | |
| about 3 years ago | 7 days ago | |
| C# | C# | |
| - | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
PhilApprovalFlow
-
Feedback on open source library.
Check it out on the link below. https://github.com/vish-j/PhilApprovalFlow.
sourcelink
-
Refix: Fast, Debuggable, Reproducible Builds
The premise of the tool seems very useful: edit debug symbols and assert messages so that source code can be found by debuggers. But this description does not make it clear how this tool accomplishes the whole task:
> Why not fix the binary coming out of the build cache, so it points to the absolute path of the source files?
What is the absolute path? If you had a virtual file system that allowed you to construct a path to any file at a given commit, this would work great. But who does that other than Google? Or if you agree that every developer will check out the same source code repo at the same path, but the you have to have the right commit checked out.
Ideally you would want your binary to point back to your code repo, like SourceLink does.
https://github.com/dotnet/sourcelink
- Visual Studio users, are there any debugging features from Rider or other IDE that you miss while using VS2022?
-
How do I include selected files from a remote repository?
Reference https://github.com/dotnet/sourcelink/tree/main/src/Microsoft.Build.Tasks.Git
-
I wrote a tiny source generator to reliably get a build timestamp, without breaking deterministic builds!
The tooling isn't quite there yet, but between SourceLink and EmbedUntrackedSources, it should be completely reasonable to be able to maintain trust (and eventually, easy, exact reproducibility) for projects that use source generation. Plus, AFAIK, for a package to truly be considered deterministic, all of the sources used for the build either must be tracked by source control, or embedded with the aforementioned flag.
-
Feedback on open source library.
It looks like your NuGet packages is missing symbols (the .pdb files next to .dll files). Symbols let folks map from compiled code back to source code. No symbols make it harder for users to debug your package. I'd recommend using Source Link for your project: https://github.com/dotnet/sourcelink
- How to get nuget package debugging to work?
-
Lessons Learned: Migrating from AppVeyor to GitHub Actions
If you want to enable Source Link for the consumers of your NuGets, make sure you turn on deterministic builds using dotnet build /p:ContinuousIntegrationBuild=true.
What are some alternatives?
runner - The Runner for GitHub Actions :rocket:
DNT - DNT (DotNetTools): Command line tools to manage .NET projects and solutions.
dnSpy
dnSpy - .NET debugger and assembly editor [Moved to: https://github.com/dnSpy/dnSpy]
sdk - Core functionality needed to create .NET Core projects, that is shared between Visual Studio and CLI
semver - Semantic Versioning Specification
ds3os - Dark Souls - Open Server
BadScript - Interpreted Programming Language written in pure C#