lllyasviel / lllyasviel/stable-diffusion-webui-forge
[Bug]: Repository update broken?
- Dominant language
- Python
- Stars
- 13k
- Forks
- 1.7k
- PR merge metrics
- No merged PRs in 30d
Description
### Checklist
- [X] The issue exists after disabling all extensions
- [X] The issue exists on a clean installation of webui
- [ ] The issue is caused by an extension, but I believe it is caused by a bug in the webui
- [X] The issue exists in the current version of the webui
- [X] The issue has not been reported before recently
- [ ] The issue has been reported before but has not been fixed yet
### What happened?
Forge's README indicates:
> Forge uses a bot to get commits and codes from https://github.com/AUTOMATIC1111/stable-diffusion-webui/tree/dev every afternoon
However the last commit in this repo is over a month ago (for both main and dev branches). A1111 just released v1.9.0 a few days ago, and I'd like to pull in the change to Forge.
### Steps to reproduce the problem
1. Open https://github.com/lllyasviel/stable-diffusion-webui-forge/commits/main/ or https://github.com/lllyasviel/stable-diffusion-webui-forge/commits/dev/
2. Open https://github.com/AUTOMATIC1111/stable-diffusion-webui/commits/master/
3. See that A1111 commits are well ahead of Forge commits
### What should have happened?
Forge repository should be automatically updated daily as indicated in the README.
### What browsers do you use to access the UI ?
Brave
### Sysinfo
--
### Console logs
```Shell
--
```
### Additional information
_No response_
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the Forge README's description of the update bot, then compare the Forge main and dev commit histories with A1111's master history using the linked pages. Determine why the daily repository update stopped; done means the documented automatic updates resume and current upstream changes are reflected in Forge.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, python
- Domain
- devops, release
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100