config file versioning ?

[Boostrix]

Duplicates

• [X] I have searched the existing issues

Summary 💡

Given the number of open PRs and issues, I feel it might make sense to version the env/yaml files - so that these can be easily updated in the future, but also to be able to make breaking changes, or provide at least a mechanism to detect what version a certain file was originally written for. Thoughts ?

(I do realize that there are plans being discussed to phase out env/yaml configs, but for the time being, it's what we've got - and adding a version flag would seem like a straightforward and useful thing to do)

Examples 🌈

No response

Motivation 🔦

No response

[k-boikov]

Each release/branch/commit has its env template included in them. What versioning do you suggest?

[Boostrix]

care to share a link to see if we're talking about the same thing ?

[k-boikov]

I understood we are talking about this file https://github.com/Significant-Gravitas/Auto-GPT/blob/master/.env.template Is that correct?

[Boostrix]

I talked about introducing a version number so that files like the env/yaml can be migrated in the future if/when the need arises

[github-actions[bot]]

This issue has automatically been marked as stale because it has not had any activity in the last 50 days. You can unstale it by commenting or removing the label. Otherwise, this issue will be closed in 10 days.

[github-actions[bot]]

This issue was closed automatically because it has been stale for 10 days with no activity.