Skip to content

English Forks and Attribution

ame824 edited this page Aug 2, 2026 · 2 revisions

Forks and attribution

autoDoIt is a publicly readable, source-available project created by ame824. The complete terms are in LICENSE.md; the short attribution notice is in NOTICE.md.

What is explicitly permitted

A public GitHub fork for personal Bitburner configuration is welcome. This especially includes changes to core/config.js and pointing the updater at the fork owner's repository. Forks used to prepare a contribution for the upstream project are permitted as well.

Copyright, credits, license, NOTICE, the link to ame824/autoDoIt, and a clear fork/change notice must remain visible.

What is not permitted

  • representing autoDoIt or substantial parts of it as an independently created original;
  • removing or obscuring copyright, credits, or provenance;
  • presenting a modified version as an official autoDoIt release;
  • publishing larger derivatives outside the license exceptions or using them commercially without prior permission.

Automated fork review

A daily GitHub Action inspects the fork network. Unmodified forks and core/config.js-only forks with intact attribution are accepted. Missing attribution or an upstream link creates an internal review finding. Changes outside configuration are marked only as requiring human review.

After setup, the workflow was started manually and completed successfully against the real fork network.

The monitor never accuses or reports anyone automatically. A person reviews a finding first. If there is a genuine problem, the first step is a friendly contact; escalation is considered only after a confirmed violation.

Current status

The currently known forks are fine: one is unmodified, while the other changes only personal configuration and keeps the attribution and upstream link.

Deutsche Version

Clone this wiki locally