You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It appears this repo served as the upstream for historical releases of Ansible Tower. It would be great if this release preserved the tags of the original repo for code reference and comparison, such as easy diffs.
My purpose of this is mostly to give students (or random developers starting a Django project again) starting out with single-page-js + Django REST Framework an example of an early evolving Django REST Framework project (and various methods of modelling access control), but also to more easily see how certain features evolved over time. In particular, Tower customized RBAC and did some things with DJRF options that were clever/useful.
This may also help those who want to craft/improve alternative setup and development instructions by exploring the non-Docker install versions of those instructions.
Environment
N/A
Steps To Reproduce:
Browse tags in GitHub, note that only a 1.0.0 is present
Expected Results:
All historical tags would still be present.
Actual Results:
Only a 1.0.0 tag is present, a release number that doesn't align with tower releases.
Additional Information:
N/A
The text was updated successfully, but these errors were encountered:
Summary
It appears this repo served as the upstream for historical releases of Ansible Tower. It would be great if this release preserved the tags of the original repo for code reference and comparison, such as easy diffs.
My purpose of this is mostly to give students (or random developers starting a Django project again) starting out with single-page-js + Django REST Framework an example of an early evolving Django REST Framework project (and various methods of modelling access control), but also to more easily see how certain features evolved over time. In particular, Tower customized RBAC and did some things with DJRF options that were clever/useful.
This may also help those who want to craft/improve alternative setup and development instructions by exploring the non-Docker install versions of those instructions.
Environment
N/A
Steps To Reproduce:
Browse tags in GitHub, note that only a 1.0.0 is present
Expected Results:
All historical tags would still be present.
Actual Results:
Only a 1.0.0 tag is present, a release number that doesn't align with tower releases.
Additional Information:
N/A
The text was updated successfully, but these errors were encountered: