Code
How alistgo/alist is laid out, and where to start for common changes.
There is no import map for this report yet.
Where to start reading
- Repository root
- Repository root
- Likely start-up file
- Suggested starting pointAI
- Suggested starting pointAI
- Suggested starting pointAI
- Suggested starting pointAI
- Suggested starting pointAI
Find files for a task
AIAdd a new storage driver
- Implement the driver.Driver interface defined in internal/driver/driver.go with Get, Put, Move, Remove operations
- Register the new driver in internal/op/driver.go's driver factory/initialization logic
- Add driver-specific configuration schema to internal/driver/config.go for setup parameters
- Test driver integration by writing unit tests similar to internal/op/driver_test.go patterns
Add a new file operation feature
- Define the operation in internal/op/fs.go alongside existing file operations (copy, link, archive)
- Implement core filesystem logic in appropriate internal/fs/ module (e.g., internal/fs/fs.go for VFS abstraction)
- Add HTTP endpoint in internal/message/http.go to expose the operation to REST API
Add a new background task type
- Define task type enum or constant in internal/task/base.go
- Implement task handler extending base task structure in internal/task/manager.go
- For async operations, integrate with pkg/task/manager.go queue infrastructure
Trace runtime behavior
Add or update tests
Change build or automation
RepoPilot lists up to 500 files, so a file missing here may still exist.
- Files marked “likely” are guessed from their names.