Detect the hash where a remote file changed
Nobody has claimed this yet.
- Dominant language
- F#
- Stars
- 2.1k
- Forks
- 528
- Avg merge
- 1d 12m
- Merged PRs (30d)
- 54
Description
Currently we detect the lastest hash of a github remote file and store it in the lock file. It would be much nicer if we can detect the last hash where a given remote file changed.
Background: many projects reference
github fsharp/FAKE src/app/FakeLib/Globbing/Globbing.fs
github fsharp/FAKE modules/Octokit/Octokit.fsx
whenever we commit to FAKE the hash of these files changes. Even when the files didn't change
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no implementation files or tests; start by tracing Paket's GitHub remote-file handling and lock-file generation for the two example references. Done means the lock file records the latest commit that changed each referenced file, rather than changing for unrelated commits to the repository.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fsharp, git, github
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100