Gitmore (<a href="https://gitmore.io" rel="nofollow">https://gitmore.io</a>) – natural language queries across GitHub, GitLab, and Bitbucket.<p>Instead of filtering PRs, scanning commit logs, or asking engineers for updates:<p>- "What shipped last week?" - "Who's been working on the API?" - "Which PRs have been open longest?" - "Summarize this month's releases"<p>Plain English in, plain English out.<p><i>How it works:</i><p>Connect your repos via OAuth. We register webhooks. Every event gets normalized into a structured schema – commit message, PR description, author, timestamp, files changed.<p>The AI queries structured data, not raw text. PR descriptions and titles carry context that individual commits often miss.<p><i>Automated reports:</i><p>Don't want to ask? Schedule it.<p>Weekly or monthly summaries delivered to Slack or email. Forward to stakeholders or let it run on autopilot.<p><i>Other features:</i> - Slack bot: Ask from where you already work - Public changelog: yourcompany.gitmore.io/changelog - Contributor leaderboard<p><i>Security:</i><p>Metadata only. We store commit messages, PR titles, descriptions, timestamps, authors.<p>We never access source code, diffs, or file contents.<p>- Token encryption: Fernet (HMAC-SHA256 + AES-128-CBC) - Webhook verification: HMAC-SHA256 - 2FA support<p>Verify yourself: check webhook settings after connecting.<p>Free for 1 repo: <a href="https://gitmore.io" rel="nofollow">https://gitmore.io</a>
返回首页
最新
Stillness quiets the noise, clarity arrives; it reveals what you already know. And what you know shapes what becomes.<p>“It’s done” is the feeling of knowing—before the world catches up.
My agency was bleeding $1,800/year on contractor Notion seats. The problem: I needed to give contractors access to specific data (CRM, project tracker) but couldn't let them see pricing, margins, or other clients' information.<p>Notion's native solution doesn't work:<p>Row-level filtering exists but it's view-only (contractors can't edit)<p>Column hiding doesn't exist<p>Guest sharing is read-only<p>So you either pay $15/mo per seat or duplicate databases (maintenance nightmare)<p>I built a permissions layer using Notion's OAuth API. It lets contractors see only specific rows and columns, edit data, all without expensive seats.<p>How it works:<p>Connect Notion via OAuth<p>Define roles: "Sales reps see only leads where owner = them, hide pricing column"<p>Contractors access a clean portal<p>They view/edit data in real-time (syncs every 5 minutes)<p>You pay $59/mo flat for unlimited users<p>The math:<p>5 contractors × $15/mo = $900/year wasted<p>20 contractors × $15/mo = $3,600/year wasted<p>50 contractors × $15/mo = $9,000/year wasted<p>With this: all of them = $59/mo flat.<p>Technical:<p>Frontend: React + TypeScript<p>Backend: Supabase + PostgreSQL (RLS)<p>Auth: Notion OAuth 2.0<p>Current state:
50 beta testers. First 20 customers get $49/month locked-in (launching at $79 after January).<p>Limitations:<p>Only Notion databases (not pages)<p>5-minute sync (not instant)<p>Requires role definition<p>No team permissions yet (roadmap)<p>The ask:
If this solves a problem you have, we'd love feedback. Are there permission use cases we're missing? What's your price sensitivity?<p>Free trial: notionportals.com
Just got laid off from a chill swe job. It was remote. F. What is the quickest way to get a chill remote job where I have responsibilities and autonomy?<p>5YOE in JS Fullstack/ Python. SF. On student visa.
What is this constant nagging? I have declined countless times on various devices and it keeps nagging. I get they need more data to train on, but lord saviour if you must offer free membership then.
First off, this thread is NOT a petition to rally against the moderation team. Considering the deluge of trash they deal with every day, I think they are doing a valiant job and are to be commended.<p>That said, its becoming more and more obvious every day that there is a tremendous amount of attempts by bots, and specifically AI agents, bombarding HN every day. I worry about the integrity of the discourse here and if the ever growing wave of slop will overtake staff resources to deal with it. Is it time to implement captcha for HN? If so, should it be out of the box, or a new mechanism more tailored to the security and privacy-centric nature of the HN readership?