今日已更新 214 条资讯 | 累计 24500 条内容
关于我们

标签:#git

找到 1255 篇相关文章

AI 资讯

Visual Cue Tracker: Mapping My Values, One Week at a Time

This is a submission for the GitHub Finish-Up-A-Thon Challenge What I Built I built the Visual Cue Tracker, a tiny, personal sanctuary for reflection. It’s a tool designed to help us map our daily actions against our core values, specifically Empathy, Growth, and Balance. I started this project because I found myself moving so fast in my software engineering studies and internships that I often forgot why I was doing what I was doing. This tracker lets me see my week at a glance, reflect on my progress, and hold space for the things that truly matter to me. Demo Deployed site: hopebestworld.github.io github repo: https://github.com/HopeBestWorld/VisualCueTracker/tree/main demo: https://youtu.be/EqVfj289e-Q The Comeback Story When I first started this project, it was just a repo with no pushed code. In 2025, I simply set up the repo and put in a description, but never put the time or effort into bringing the idea to life. To finish it up for the challenge, I added a few things that made it feel truly alive. I built a custom, zero-key AI engine that runs entirely inside your browser. It scans your weekly reflections and gives you immediate, gentle feedback on how well your written thoughts match the values you logged. It suggests! If I’m missing the mark, it gives me specific prompts to help me get back to my goals. I added quick-export features so I can turn my weekly reflections into a clean text log, making it easy to keep a personal journal outside of the app. I set up a fully automated deployment pipeline using GitHub Actions, so my site updates instantly whenever I push my code. My Experience with GitHub Copilot GitHub Copilot felt like a supportive coding partner throughout this journey. When I was stuck on complex pathing issues for my GitHub Pages deployment, it helped me iterate through solutions quickly. It was especially great at explaining why certain parts of my code (like my custom Regex AI engine) were behaving the way they were, allowing me to stay in

2026-06-07 原文 →
AI 资讯

Finishing What I Started: A Code Snippet Manager Built on GitHub Gists

This is a submission for the GitHub Finish-Up-A-Thon Challenge What I Built ASTronaut is a personal code snippet manager that uses GitHub Gists as its storage backend. The name is a dumb pun: it literally builds an AST (Abstract Syntax Tree) of your Java snippets using JavaParser, pulling out class and method names so you can search by structure, not just by file name. The idea is simple: stop losing useful snippets to random notes apps or Gist pages you'll never find again. ASTronaut gives you a proper UI to create, search, edit, diff, and organize your snippets, while keeping everything synced to GitHub Gists so nothing is stuck on one machine. Frontend Repository: https://github.com/kusoroadeolu/astronaut-ui Backend Repository: https://github.com/kusoroadeolu/ASTronaut The Comeback Story The original ASTronaut had PostgreSQL, Redis, Spring Security, JWT auth, a full login/register flow, user management, admin roles, rate limiting... for a tool that only I was ever going to use. It never shipped. Not because it didn't work, but because every time I sat down to actually use it, I had to spin up a database, a Redis instance, deal with tokens. It just killed any motivation I had. The whole point was to save me time. It wasn't doing that. So it sat there. For a while. When I heard about the Finish-Up-A-Thon, this was the first project that came to mind. What Actually Changed The revamp had one goal: make it feel like a tool, not a project. Here's what got cut: The entire auth system: Spring Security, JWT, login/register, user management, all of it PostgreSQL and JPA, replaced by a lightweight local JSON index file Redis and rate limiting, pointless for a solo local tool Deep metadata extraction that was never actually used in search Here's what replaced it: GitHub PAT in an application.props file. One line of config, no OAuth flow, no callback URLs. PAT is the right call here: OAuth is for when other people are logging in with their GitHub accounts. This is just me. G

2026-06-07 原文 →