-
Notifications
You must be signed in to change notification settings - Fork 6
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
feat: show commit list #917
Conversation
Is there an issue/epic for this? |
@rokroskar yes, it's #852 . I accidentally wrote twice #623 in the issue description (fixed) but it was in the |
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.
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.
It looks really good!
I also have a small details i would change, could you remove the line on top of the beginning of commits?
Here it would be on top of April.... I think with pt-0 inside the card you can make it happen
I would also align the three buttons to the right on the header and add a tooltip to the commits count.
@ciyer good point! We may want to handle pagination better in the future, but in the meanwhile that message would make this limitation clear. Here is a comparison (first is the current implementation). The final implementation has |
@vfried thanks for the suggestions! I think the current spacing on the top is in line with the other tabs (see Description and Stats). Furthermore, making the top padding Im not sure about moving the buttons to the right. I see that it would make the page more similar to the |
Nice! I prefer the second one, the plain text option. The InfoAlert looks a bit too aggressive to my eyes. |
92e0069
to
81a09e7
Compare
@ciyer done |
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.
Looks great! Can't wait to have this feature on Renkulab. I pushed two small commits:
- Fix a warning about duplicate React component keys
- Add padding to the commit list in the merge request view so it looks the same as in the project commit view.
src/utils/Commits.js
Outdated
<SingleCommit | ||
key={commit.id ? commit.id : commit.readableDate} | ||
key={commit.id ? commit.id : `${i}-${commit.readableDate}`} |
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.
the same readableDate
shouldn't appear twice. If that happens, it may be a bug in how the date is computed
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.
Using committed_date
instead of authored_date
seems to be the right thing to do to avoid out of order dates. It's also in line with what GitLab shows
Adds all the necessary logic to handle project's commits: * Add a new tab in project overview to show commits * Create ProjectCoordinator with basic metadata * Create higher order function to easily map project data from global store to React components fix #852
0587815
to
4e38152
Compare
|
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.
👍
The new changes look really good, I agree with you with the buttons and the top padding thing is a small detail. I see inside stats is a similar thing so it's ok if you leave it as it is. |
Adds all the necessary logic to handle project's commits: * Add a new tab in project overview to show commits * Create ProjectCoordinator with basic metadata * Create higher order function to easily map project data from global store to React components fix #852
4e38152
to
e9ca00c
Compare
I had to rebase, could someone please re-approve? |
Adds all the necessary logic to handle projects commits.
It includes a
ProjectCoordinator
component to handle storing project data to the global Redux store (#623). This created extra difficulties since we can't easily migrate all theProjectModel
logic at once. To simplify the temporary co-existence, I created a higher order functionwithProjectMapped
to map project data from the global store to single components whenever needed.The first commit closes #852 by adding a new "Commits" section in the project overview tab, while the second commit re-uses the
CommitsView
component in the merge request section.The third commit injects all the commits-related logic in the environments components. We may want to clean up a little bit
Notebooks.container.js
whenbranches
will be managed byProjectCoordinator
.Preview: https://lorenzotest.dev.renku.ch
How to test: browse to any project, go to the new "Commits" section on the "Overview" page. Please check also the "Merge request" section and check a notebook in the "File" tab, starting also a new environment from there. This should cover all the relevant changes.