-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
Re-sync Repository from VCS #6210
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.
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@stsewd This looks better I think :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Co-Authored-By: Manuel Kaufmann <[email protected]>
Co-Authored-By: Manuel Kaufmann <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Thanks for taking the suggestions!
The difference is that the sync versions button doesn't apply only for active versions, but for inactive versions as well. |
You may have a point. Although, having a button outside the title of the page didn't look good to me: seems broken style. The "Sync" does not affect "Active versions", it only affect "Inactive versions" for now --because there is no automated rules yet. So, at this moment, the right place would be under "Inactive versions". We do need to place it somewhere, and I'm not seeing a perfect place for it. I suggest to leave it below "Active versions". |
Actually it does, it activates a version if it follows semver and it's greater than the current stable. Also it updates latest and stable. |
OK. So, it makes more sense to be below the "Active versions" then 😄 |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
I think this is a good interim UI, but I don't think it's quite ready. I think the better approach here is to make it an actual part of the page, with copy that explains what it does. Currently "Sync Versions" doesn't really mean anything to many users, and will likely be confusing. It seems like it would be more valuable with some copy that explains that it will update the versions from the VCS provider, and what that will do. |
I like to avoid putting copy in UI, it clutters the UI and is often just going to be skipped by the user. I think a refresh icon button communicates more that "resync versions" and doesn't require us to explain our UI. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changes look good, i noted some UI changes.
I think there will be a better UX here if we rely on a publictask or API call, similar to the import refresh call, and we can avoid communicating task progression through notification messages. This is a good first step for now, a good UX solution will add more complexity to get UI state correct.
else: | ||
messages.error( | ||
request, | ||
_("There was an error when syncing project's versions"), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same feedback here, but also: there isn't much the user can do with this error. Do we have any additional information we can display in the sync
variable? What error does a failure with the sync task point at otherwise? Perhaps there is more guidance that we can give the user.
As for the message, it's better to speak to the user -- something closer to:
_("There was an error when syncing project's versions"), | |
_("There was a problem updating the project versions"), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@agjohnson Actually sync_versions
function only calls a celery task sync_repository_task
So, I don't know if we can show much more information from sync
variable.
<li> | ||
<form method="post" action="{% url 'project_version_sync' project_slug=project.slug %}"> | ||
{% csrf_token %} | ||
<input type="submit" value="{% trans 'Sync Versions' %}"> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think a refresh icon button probably communicates what we need here and doesn't require us to add copy to our UI.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Okay :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Co-Authored-By: Anthony <[email protected]>
Co-Authored-By: Anthony <[email protected]>
…into project-resync
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
I think this is still valid |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
@agjohnson would be good for you to take a peek here. I think it's probably worth integrating into the new design. |
@agjohnson what are the next actionable steps for this PR? Should we resolve conflicts and merge it so it's included in the new templates? |
This PR works over the old templates, so I don't think it makes too much sense to try to recover it since we will need to migrate it to https://github.com/readthedocs/ext-theme anyways. There is some backend work we could recover once we implement this on ext-theme, tho. I'm closing this PR for now since we haven't had the time to prioritize it anyways. |
No description provided.