ScottArbeit
Update all date references and Git's age in markdown documentation for 2025
Please review all markdown (.md) files in the repository and update the following:
- Any reference to how long Git has been in existence (number of years, phrases like "over X years," etc.) should be updated to reflect the current year—2025.
- Review and update all dates, years, or lengths of time mentioned in the documentation (e.g., "as of 2023," "in 2018," "over the last 5 years") so that the docs remain current and fresh for 2025.
- Ensure any statements about technologies, standards, or time-sensitive events are also updated where appropriate.
This will help keep our documentation accurate and modern for readers.
It might make more sense to reword some date references so that they are evergreen. In other words, refer to the year Git started, instead of how many years ago that was.
Oh, I just chose this as a test for some preview Copilot features I wanted to play with. Nothing serious. As a GitHub employee I have access to early feature ships.
What’s your interest in Grace?
If the feature includes date calculations, you could test it my way also, and have a better result.
What’s your interest in Grace?
My preference for version control (Breezy) is not popular, so I watch other projects that are trying to solve the same problem. Grace sounds good, except for its centralization and autosave, since there are those that aren't connected and those that don't want every mistake immortalized in the repo. (I am unaware of how much disk space a repo takes, but if it is more than Git and friends, then it's too much.)