New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Perforce: `p4-fusion` admin issues #51536

Open

4 of 7 tasks

peterguy opened this issue May 5, 2023 · 0 comments

Labels

Contributor

peterguy commented May 5, 2023 •

edited by sourcegraph-bot-devx

Loading

Plan

Track issues related to administering p4-fusion

Tracked issues

Allow the admin to configure a Perforce client name to match a naming convention #51235 👩

@peterguy: 9.00d

First-Class Perforce: Tracking issue #50247 2.00d
- Add documentation about memory requirements for running p4-fusion #42450 👩 🏳️ First-class Perforce Documentation
- (🏁 2023-06-15) Perforce: Empty repo but no log messages to help explain why #43121 (PRs: ~~#51598~~) 2.00d 🐛👩 🏳️ First-class Perforce QoL and Bugfixes

Completed: 9.00d

(🏁 2023-05-17) Check memory before cloning a large Perforce depot (or monitor for OOM) #42385 (PRs: ~~#51284~~) 5.00d 👩
(🏁 2023-06-15) Perforce: Empty repo but no log messages to help explain why #43121 (PRs: ~~#51598~~) 2.00d 🐛👩 🏳️ First-class Perforce QoL and Bugfixes
(🏁 2023-06-15) Files don't sync from Perforce depot #50860 (PRs: ~~#51598~~) 2.00d

Legend

👩 Customer issue
🐛 Bug
🧶 Technical debt
🎩 Quality of life
🛠️ Roadmap
🕵️ Spike
🔒 Security issue
🙆 Stretch goal

The text was updated successfully, but these errors were encountered:

peterguy added tracking perforce-p4-fusion-admin labels

sourcegraph-bot-devx mentioned this issue

First-Class Perforce: Tracking issue #50247

Open

55 tasks

eseliger removed the perforce-p4-fusion-admin label

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment