GitShow/facebook/dotslash-publish-release
facebook

dotslash-publish-release

Create DotSlash files for GitHub releases

by facebook
Star on GitHubForkWebsite

Python

9 stars4 forks4 contributorsQuiet · 7mo agoSince 2024MIT

Meet the team

See all 4 on GitHub →
bolinfest
bolinfest4 contributions
bigfootjon
bigfootjon3 contributions
dtolnay
dtolnay1 contribution
valt-x
valt-x1 contribution

Languages

View on GitHub →
Python95.2%
Dockerfile4.8%

Commit activity

Last 12 weeks · 0 commits

Full graph →

Community health

4 of 6 standards met

Community profile →
75
✓README✓License✓Contributing✓Code of Conduct○Issue Template○PR Template

Recent PRs & issues

Quiet · 1 discussion · Last activity 7mo ago
See all on GitHub →
bigfootjon
Failure when dotslash path is a directoryOpenIssue

I've been working on using this job for a private github repo and there is a folder with the same name as the target binary so it fails with this error: I think this can be fixed by using a different path as the default location

bigfootjon · 2y ago

Recent fixes

View closed PRs →
valt-x
feat: embed build metadata in generated dotslash filesMergedPR

Add build metadata collection from GitHub Actions environment Include source config path, CI information, and generation timestamp Add CI job URL for traceability back to the generating workflow Support disabling metadata via include-build-metadata input Update action.yml to expose new input parameter Add comprehensive documentation with examples Fixes #2

valt-x · 7mo ago
bigfootjon
Embed build metadata in the generated dotslash fileClosedIssue

In the Meta-internal version of dotslash we have a header with some valuable information: the source file used to generate the dotslash file and the CI job that actually generated the file. Meta employees can see an example of this header here: https://fburl.com/code/l0euqzmy Would this be something we could consider adding to this action? All relevant information could be derived without any input from users. Another related feature request is arbitrary extra metadata, though I don't have a concrete need for it at this time. Ref https://github.com/facebook/buck2/pull/565 for the inspiration behind this feature request

bigfootjon · 7mo ago
bigfootjon
Use a temp folder for the outputMergedPR

This avoids conflicts between repo contents and the result of the action creation process. Not entirely sure if this is the right solution or not Closes: https://github.com/facebook/dotslash-publish-release/issues/3

bigfootjon · 2y ago
Structured data for AI agents

Repository: facebook/dotslash-publish-release. Description: Create DotSlash files for GitHub releases Stars: 9, Forks: 4. Primary language: Python. Languages: Python (95.2%), Dockerfile (4.8%). License: MIT. Homepage: https://dotslash-cli.com Open PRs: 0, open issues: 1. Last activity: 7mo ago. Community health: 75%. Top contributors: bolinfest, bigfootjon, dtolnay, valt-x.

·@ofershap

Replace github.com with gitshow.dev