Open
Conversation
…cloud env The py-pho-timeline package (pyPhoTimeline repo) is not publicly available on GitHub. Removed it from dependencies and sources to allow uv sync to succeed. Lockfile regenerated with mne from local fork, phopylslhelper, phopymnehelper from cloned repos. Co-authored-by: Pho Hale <CommanderPho@users.noreply.github.com>
Co-authored-by: Pho Hale <CommanderPho@users.noreply.github.com>
|
Cursor Agent can help with this pull request. Just |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Set up the development environment by removing an inaccessible dependency and documenting the setup process.
The
py-pho-timelinerepository is not publicly available, preventing a cleanuv sync. This PR removes it as a dependency frompyproject.tomland updatesuv.lock. Additionally,AGENTS.mdis added to document the necessary steps for setting up the development environment, including cloning sibling repositories and handling a specificmneversioning workaround, ensuring future environment setups are smooth.