Skip to content

Commit

Permalink
Merge pull request #25 from t4d-gmbh/20-news-feed-vs-git-history
Browse files Browse the repository at this point in the history
20 news feed vs git history
  • Loading branch information
matteodelucchi authored Oct 25, 2024
2 parents 3803ecb + 31f8ac1 commit 0ac7e1f
Show file tree
Hide file tree
Showing 3 changed files with 42 additions and 1 deletion.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Original file line number Diff line number Diff line change
@@ -1,3 +1,44 @@
#### News Feed ⚡ <i class="fab fa-git"></i> History

_TODO: show pull request activity and related git log
{% if build == "pages" %}

The <i class="fab fa-github"></i> or <i class="fab fa-gitlab"></i> News Feed provides a broad overview of recent activities, the <i class="fab fa-git"></i> History provides a detailed and structured view of the project’s evolution.
Both tools help to track changes, discuss ideas, understand references to related topic (issues, merge/pull requests, etc.) and make project management and collaboration more efficient.

##### News Feed

The <i class="fab fa-github"></i> News Feed provides a high-level overview of activities in the repositories.
It includes updates such as new commits, pull requests, issues, and comments.
This feed is useful for quickly catching up on recent changes and interactions within the project but also for getting a sense of the project's overall activity and progress.
Additionally, it can help you stay informed about the work being done by other contributors and provide opportunities for collaboration and feedback.

![GitHub News Feed](./github_news_feed.png)

##### <i class="fab fa-git"></i> History

<i class="fab fa-git"></i> History, on the other hand, offers a detailed view of the changes made to your codebase locally and remotely.
It provides a chronological record of commits, branches, merges, and other actions that have occurred throughout the project's history.
By using commands like `git log`, you can visualize the commit history in a concise and graphical format.
This is particularly useful for understanding the sequence of changes and how different branches and merges have evolved over time.
It also allows you to navigate through the project's history, compare different versions of the code, and identify the changes that have been made by you and other contributors without the need for a web interface.
This can be helpful for debugging issues, reverting changes, and understanding the context of specific commits.

![Git Log Graph](./git_log_graph.png)

Compared to the News Feed, it does not provide real-time updates or notifications about recent activities and interactions.

{% else %}

::::{grid}
:::{grid-item-card} News Feed
Overview of **repository activities** (commits, pull requests, issues, comments).
Useful for quick *updates* and *collaboration*.
![GitHub News Feed](./github_news_feed.png)
:::
:::{grid-item-card} <i class="fab fa-git"></i> History
Detailed record of **codebase changes** (commits, branches, merges).
Useful for understanding project *evolution* and *debugging*.
![Git Log Graph](./git_log_graph.png)
:::

{% endif %}

0 comments on commit 0ac7e1f

Please sign in to comment.