Skip to content

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

Closed
wants to merge 13 commits into from
Closed

Conversation

saadmk11
Copy link
Member

@saadmk11 saadmk11 commented Sep 26, 2019

No description provided.

@saadmk11 saadmk11 requested review from ericholscher and a team September 26, 2019 13:49
Copy link
Member

@stsewd stsewd left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me. I think the button should be placed in another place, like above Active versions, to the right.
Screenshot_2019-09-26 Versions Read the Docs

@saadmk11
Copy link
Member Author

@stsewd This looks better I think :)

Screenshot from 2019-09-27 00-14-19

@saadmk11 saadmk11 requested a review from stsewd September 26, 2019 18:16
@stsewd stsewd requested a review from a team September 26, 2019 18:43
Copy link
Member

@humitos humitos left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! The PR looks good to me.

I left some suggestions about class naming and button label. Also, I think that we should move the button below the "Active Versions" title, to keep consistency with the "Builds" page, for example:

Screenshot_2019-10-09_13-30-39

@saadmk11 saadmk11 requested a review from humitos October 9, 2019 13:46
@saadmk11 saadmk11 closed this Oct 9, 2019
@saadmk11 saadmk11 reopened this Oct 9, 2019
Copy link
Member

@humitos humitos left a 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!

@stsewd
Copy link
Member

stsewd commented Oct 10, 2019

I think that we should move the button below the "Active Versions" title, to keep consistency with the "Builds" page, for example:

The difference is that the sync versions button doesn't apply only for active versions, but for inactive versions as well.

@humitos
Copy link
Member

humitos commented Oct 11, 2019

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".

@stsewd
Copy link
Member

stsewd commented Oct 11, 2019

The "Sync" does not affect "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.

@humitos
Copy link
Member

humitos commented Oct 11, 2019

OK. So, it makes more sense to be below the "Active versions" then 😄

@stale
Copy link

stale bot commented Nov 25, 2019

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.

@stale stale bot added the Status: stale Issue will be considered inactive soon label Nov 25, 2019
@stsewd stsewd removed the Status: stale Issue will be considered inactive soon label Nov 25, 2019
@stsewd stsewd requested a review from a team November 25, 2019 18:59
@ericholscher
Copy link
Member

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.

@agjohnson
Copy link
Contributor

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.

Copy link
Contributor

@agjohnson agjohnson left a 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"),
Copy link
Contributor

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:

Suggested change
_("There was an error when syncing project's versions"),
_("There was a problem updating the project versions"),

Copy link
Member Author

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' %}">
Copy link
Contributor

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.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Okay :)

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have added this one:
Screenshot from 2019-11-29 01-33-27

Another option might be:
Screenshot from 2019-11-29 01-33-11

@saadmk11 saadmk11 requested a review from agjohnson November 28, 2019 19:39
@stale
Copy link

stale bot commented Jan 12, 2020

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.

@stale stale bot added the Status: stale Issue will be considered inactive soon label Jan 12, 2020
@saadmk11
Copy link
Member Author

I think this is still valid

@stale stale bot removed the Status: stale Issue will be considered inactive soon label Jan 13, 2020
@stale
Copy link

stale bot commented Feb 27, 2020

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.

@stale stale bot added the Status: stale Issue will be considered inactive soon label Feb 27, 2020
@stsewd stsewd added Accepted Accepted issue on our roadmap and removed Status: stale Issue will be considered inactive soon labels Feb 27, 2020
@ericholscher
Copy link
Member

@agjohnson would be good for you to take a peek here. I think it's probably worth integrating into the new design.

@humitos
Copy link
Member

humitos commented Feb 22, 2022

@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?

@humitos
Copy link
Member

humitos commented Aug 9, 2023

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.

@humitos humitos closed this Aug 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Accepted Accepted issue on our roadmap
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants