d9gsc7uj9r
    • Create new note
    • Create a note from template
      • Sharing URL Link copied
      • /edit
      • View mode
        • Edit mode
        • View mode
        • Book mode
        • Slide mode
        Edit mode View mode Book mode Slide mode
      • Customize slides
      • Note Permission
      • Read
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Write
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
    • Invite by email
      Invitee

      This note has no invitees

    • Publish Note

      Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note No publishing access yet

      Your note will be visible on your profile and discoverable by anyone.
      Your note is now live.
      This note is visible on your profile and discoverable online.
      Everyone on the web can find and read all notes of this public team.

      Your account was recently created. Publishing will be available soon, allowing you to share notes on your public page and in search results.

      Your team account was recently created. Publishing will be available soon, allowing you to share notes on your public page and in search results.

      Explore these features while you wait
      Complete general settings
      Bookmark and like published notes
      Write a few more notes
      Complete general settings
      Write a few more notes
      See published notes
      Unpublish note
      Please check the box to agree to the Community Guidelines.
      View profile
    • Commenting
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
      • Everyone
    • Suggest edit
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
    • Emoji Reply
    • Enable
    • Versions and GitHub Sync
    • Note settings
    • Note Insights New
    • Make a copy
    • Transfer ownership
    • Delete this note
    • Save as template
    • Insert from template
    • Import from
      • Dropbox
      • Google Drive
      • Gist
      • Clipboard
    • Export to
      • Dropbox
      • Google Drive
      • Gist
    • Download
      • Markdown
      • HTML
      • Raw HTML
Menu Note settings Note Insights Versions and GitHub Sync Sharing URL Create Help
Create Create new note Create a note from template
Menu
Options
Make a copy Transfer ownership Delete this note
Import from
Dropbox Google Drive Gist Clipboard
Export to
Dropbox Google Drive Gist
Download
Markdown HTML Raw HTML
Back
Sharing URL Link copied
/edit
View mode
  • Edit mode
  • View mode
  • Book mode
  • Slide mode
Edit mode View mode Book mode Slide mode
Customize slides
Note Permission
Read
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Write
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
  • Invite by email
    Invitee

    This note has no invitees

  • Publish Note

    Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note No publishing access yet

    Your note will be visible on your profile and discoverable by anyone.
    Your note is now live.
    This note is visible on your profile and discoverable online.
    Everyone on the web can find and read all notes of this public team.

    Your account was recently created. Publishing will be available soon, allowing you to share notes on your public page and in search results.

    Your team account was recently created. Publishing will be available soon, allowing you to share notes on your public page and in search results.

    Explore these features while you wait
    Complete general settings
    Bookmark and like published notes
    Write a few more notes
    Complete general settings
    Write a few more notes
    See published notes
    Unpublish note
    Please check the box to agree to the Community Guidelines.
    View profile
    Engagement control
    Commenting
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    • Everyone
    Suggest edit
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    Emoji Reply
    Enable
    Import from Dropbox Google Drive Gist Clipboard
       Owned this note    Owned this note      
    Published Linked with GitHub
    • Any changes
      Be notified of any changes
    • Mention me
      Be notified of mention me
    • Unsubscribe
    <p>你可能已经遇到过这种局面:策略想得很清楚,一到实盘就手软;或者相反,情绪上头追涨杀跌,回头一看全是“本来不该做”的单子。很多人搜索ea量化是什么,其实是在找一种更可复制、可约束、可复盘的交易方式。</p> <p>在我们与不同体量的交易团队合作中,一个共同结论是:决定长期结果的不是“灵感”,而是流程与纪律。ex-traders 长期专注于把主观想法拆成可执行规则,再把规则落到自动化与风控体系里,让策略能被验证、被监控、被迭代。</p> <p>更直接地说,ea量化是什么?它是把交易策略写成程序(EA/算法),让系统按照固定条件自动扫描、下单、管理仓位与退出,并用数据评估策略在不同市场环境下的表现。它的核心不是“自动赚钱”,而是“把交易变成可测试的工程”。如果你想进一步了解实战落地路径,也可以参考 <a href="https://www.ex-traders.com/">ea量化是什么</a> 的相关方法论与案例。</p> <h2>Key Takeaways</h2> <ul> <li>先用回测验证策略边界,再决定是否进入小资金实盘测试阶段。</li> <li>把入场、加减仓、止损止盈写成可量化规则,避免临盘改口径。</li> <li>用最大回撤与连续亏损阈值设置“强制停机”,防止策略失控。</li> <li>区分趋势、震荡、消息三类环境,为同一EA准备不同参数方案。</li> <li>每周复盘滑点、点差与成交率,确认收益来自策略而非运气。</li> </ul> <p>Quick Answer:ea量化是什么?它是用EA程序把交易策略自动执行与量化评估的一套方法。EA会按照规则寻找信号、控制风险并管理订单。关键在于回测、前向测试与风控阈值,而不是盲目追求全自动。</p> <h2>Table of Contents</h2> <ul> <li><a href="definition-and-scope">ea量化的定义与边界</a></li> <li><a href="how-ea-works">EA量化交易如何运作</a></li> <li><a href="data-and-backtesting">数据、回测与前向测试:验证才是核心</a></li> <li><a href="strategy-design">策略设计:从想法到可执行规则</a></li> <li><a href="risk-and-position-sizing">风控与仓位:让策略活得更久</a></li> <li><a href="tooling-and-ops">工具与运维:实盘运行的隐形成本</a></li> <li><a href="case-study">案例研究:ex-traders 如何把策略做成可复用系统</a></li> <li><a href="common-failures">常见误判与失败信号:何时不该用EA量化</a></li> <li><a href="future-trends-2026">2026趋势:监管、成本与AI对量化的影响</a></li> <li><a href="conclusion">Conclusion</a></li> <li><a href="references">References</a></li> <li><a href="faq">FAQ</a></li> </ul> <p>Methodology:本文的观点来自三类验证路径:一是对多品种交易日志进行结构化复盘(入场理由、执行偏差、风控触发);二是采用统一回测框架对参数敏感性、样本外稳定性与滑点评估;三是参考2023-2026年行业报告与公开研究,对成本与市场微结构变化进行交叉核验。</p> <h2 id="definition-and-scope">ea量化的定义与边界</h2> <p>“EA量化”常被误解成“装上就能跑、跑了就赚钱”。真实定义更克制:EA(Expert Advisor)是一种自动化执行程序;量化是用数据与规则描述策略,并用统计与实验验证其可重复性。两者结合,才构成你在搜索ea量化是什么时真正需要的那套闭环:规则化、自动化、可评估、可迭代。</p> <p>边界同样重要。EA量化不擅长处理不可量化的信息(例如突发监管、黑天鹅消息的语义不确定性),也不保证穿越所有行情。它更像一台工业机床:在适配的材料与工序里稳定输出;在错误材料上只会更快报废。</p> <h3>EA量化和“手动下单+指标”有什么本质区别?</h3> <p>本质区别在“可重复与可审计”。手动交易往往在同一信号上做出不同反应,结果无法归因;EA量化则把条件写死、把风控写明、把执行记录完整保存,从而能复盘每一笔亏损来自信号失效、成本上升还是参数不稳。这种可审计性,才是长期改进的起点。</p> <h2 id="how-ea-works">EA量化交易如何运作</h2> <p>一套可运行的EA系统通常包含四层:信号生成(何时进场)、过滤条件(何时不进)、仓位与风险(下多大、亏多少停)、交易管理(移动止损、分批止盈、超时退出)。你可以把它想成“把交易流程写成代码”,而不是“把指标搬进程序”。</p> <p>很多新手失败在把EA当成单点工具:只盯着入场信号,忽略执行与成本。现实里,点差扩大、滑点、延迟、成交失败、隔夜利息,都会让回测曲线在实盘里变形。你要把这些因素当成系统的一部分去设计与监控。</p> <div> <p>Pro Tip:如果你只做一件事,把EA日志改成“可读的交易叙事”。每笔订单输出:触发条件、过滤原因、风险预算、成交信息与退出逻辑。这样你复盘时不是看一堆数字,而是在读一段可追责的记录。</p> </div> <h3>EA量化是不是越高频越好?</h3> <p>不一定。高频意味着更依赖低延迟基础设施与更敏感的交易成本,优势往往被点差与滑点吞噬。多数个人与小团队更现实的路径是中低频:用更稳的结构信号与更严格的风险预算,换取对成本与执行不确定性的容忍度。先能稳定活下来,再谈频率。</p> <h2 id="data-and-backtesting">数据、回测与前向测试:验证才是核心</h2> <p>EA量化的“量化”两个字,主要体现在验证。回测不是拿来炫耀收益率,而是用来回答三个问题:策略在不同市场状态下是否仍有优势?收益是否被少数极端行情贡献?成本与执行扰动下是否还能站得住?</p> <p>根据多家行业研究在2024-2025年对算法交易与市场微结构的讨论,一个反复出现的结论是:交易成本的微小变化,会对短周期策略的净收益产生不成比例的影响。对EA而言,这意味着你必须把点差、滑点、延迟与成交概率纳入回测假设,并在前向测试中核对。</p> <ul> <li>成本建模:至少做三档情景(理想、常态、压力),对净收益与回撤重新评估。</li> <li>样本外测试:把最近一段行情完全隔离,禁止“看着答案调参”。</li> <li>稳健性检查:用参数扰动测试(例如止损、均线周期微调)看策略是否脆弱。</li> <li>风控回测:单独回测仓位规则,确保回撤收敛且不依赖运气反弹。</li> </ul> <ol> <li>Scan 历史数据的缺口、跳点与异常成交,先清洗再回测。</li> <li>Mark 市场分段(趋势、震荡、消息冲击),记录策略在哪些段落失效。</li> <li>Confirm 在不同成本档位下的净收益与最大回撤,避免只看毛收益。</li> <li>Manage 用小资金前向测试至少数周,核对滑点、成交率与时区差异。</li> <li>Review 每周做一次“假设对账”,不达标就暂停并回到模型修正。</li> </ol> <h2 id="strategy-design">策略设计:从想法到可执行规则</h2> <p>把想法写成EA,最难的不是代码,而是把“感觉”翻译成规则。你需要回答:触发条件是什么?确认条件是什么?无效条件是什么?退出条件是什么?以及最关键的:风险预算是多少?</p> <p>一个实用的写法是“先写交易宪法”。例如:单笔最多亏损账户权益的0.5%-1%;连续亏损N笔或回撤达到阈值必须停机;某些时段(重大数据公布前后)禁止开新仓。宪法先行,信号才有意义。</p> <table> <tr> <th>策略/场景类型</th> <th>Best For</th> <th>Risk Level</th> <th>Typical Mistake</th> </tr> <tr> <td>趋势跟随(4H/日线)</td> <td>波动扩张、单边行情较多的品种</td> <td>中</td> <td>止损过紧导致频繁被扫,错过主趋势</td> </tr> <tr> <td>震荡均值回归(15M-1H)</td> <td>区间明确、点差稳定的时段</td> <td>中高</td> <td>在趋势初期逆势加仓,回撤迅速放大</td> </tr> <tr> <td>突破策略(伦敦/纽约开盘)</td> <td>开盘波动大、成交活跃时段</td> <td>高</td> <td>忽略滑点与假突破过滤,净收益被成本吃掉</td> </tr> <tr> <td>新闻过滤型策略(低频)</td> <td>希望避开数据冲击的稳健交易者</td> <td>低中</td> <td>过滤过度导致机会太少,统计优势不足</td> </tr> <tr> <td>多策略组合(趋势+回归)</td> <td>追求曲线更平滑、适应多环境</td> <td>中</td> <td>相关性评估缺失,风险在同一时段叠加爆发</td> </tr> </table> <h3>新手应该先从哪类EA策略开始?</h3> <p>建议从低频、规则清晰、可解释的策略开始,例如趋势跟随或带过滤的突破,而不是复杂网格或无限加仓型均值回归。低频更容易验证成本影响,也更容易在日志里看懂每一笔交易为什么发生。你能解释,才有资格自动化。</p> <h2 id="risk-and-position-sizing">风控与仓位:让策略活得更久</h2> <p>EA量化的优势在一致性,风险也在一致性:如果你的规则会在坏环境里持续做错,它也会“稳定地亏”。所以风控不是附属品,而是系统的主梁。</p> <p>我们常用的三道闸口:单笔风险预算(例如0.5%权益)、日内/周内最大亏损、以及最大回撤停机。停机不是失败,而是把损失限制在可修复范围内。很多账户崩盘都不是因为一次亏损,而是因为“亏了还在加速执行”。</p> <div> <p>Pro Tip:把“连续亏损”当成策略状态变量。比如连续亏损达到6笔,自动降低仓位50%;达到10笔,直接停机并进入诊断清单(成本、滑点、行情分段、参数漂移)。这比情绪化手动干预更可靠。</p> </div> <blockquote> <p>“当我们把停机阈值写进系统后,交易体验反而更轻松:亏损出现时,我们不再纠结是不是要‘扛一下’,系统会替我们做一致的决定。”</p> </blockquote> <h2 id="tooling-and-ops">工具与运维:实盘运行的隐形成本</h2> <p>很多人把EA写出来就以为完成了90%,但实盘里真正的难点是运维:服务器稳定性、时区与夏令时、交易商的执行差异、断线重连、报价源异常、以及版本更新带来的回归Bug。</p> <p>运维做得好,才能把“理论优势”变成“可交付结果”。例如:你需要监控交易频率是否异常升高、平均滑点是否飙升、点差是否在某些时段结构性扩大、是否出现重复下单或漏单。监控要能触发告警,告警要能触发动作。</p> <p>如果你正在梳理完整的落地清单,可以在策略研究阶段就把 <a href="https://www.ex-traders.com/">ea量化是什么</a> 作为对照框架:信号、风控、执行、监控、复盘五件事缺一不可。</p> <h2 id="case-study">案例研究:ex-traders 如何把策略做成可复用系统</h2> <p>我第一次把一个“看图下单”的策略改造成EA时,最大的冲击不是收益变化,而是我终于看清了自己过去到底在做什么:很多“经验”其实是临时找理由。我们在ex-traders 的工作方式是先把策略拆成可证伪的假设,再决定是否值得进入工程化。</p> <p>一个典型项目是为偏趋势的交易者构建“结构突破+过滤+分批退出”的EA。初版回测很漂亮,但前向测试第二周开始净值波动明显增大。我们把日志按“失败类型”分类后发现:主要问题不是信号,而是开盘时段滑点上升导致止损形态被破坏,进而触发更差的退出。</p> <p>我的处理步骤很“无聊”,但有效:第一,加入时段过滤,避开最容易滑点失真的分钟区间;第二,改用更宽的初始止损+更保守的仓位,让执行扰动不会把策略结构打碎;第三,把成交失败与重试逻辑写进EA,避免断线时出现重复订单。调整后,收益率没有回测那么“耀眼”,但最大回撤收敛,曲线更像一个能长期运行的系统。</p> <p>另一次我们遇到的反直觉结果是:减少交易次数反而提高了净收益。原因很现实:当我们把过滤条件写得更严格,把最拥挤、成本最高的信号段剔除后,净收益变得更“干净”,策略优势不再被手续费与滑点稀释。这个阶段我们也会让用户回到最基础的问题:你要的到底是更高的收益率,还是更高的可交付概率?这也是很多人理解ea量化是什么时容易忽略的目标定义。</p> <blockquote> <p>“以前我以为EA是替我赚钱的机器。后来我才明白,它更像一套纪律系统:它逼我把每个决策写清楚,并接受数据的审判。”</p> </blockquote> <h2 id="common-failures">常见误判与失败信号:何时不该用EA量化</h2> <p>EA量化并非适合所有人,也并非适合所有策略。你需要识别“该暂停”的信号,而不是用更多参数去掩盖问题。</p> <h3>为什么很多EA回测很好,实盘却走样?</h3> <p>最常见原因是过拟合与成本缺失。回测中你可能使用了理想点差、没有真实滑点,或不断微调参数让它“贴合历史”。一到实盘,成交与成本扰动把边际优势吃掉,策略就从“统计优势”变成“随机波动”。解决思路是样本外验证、成本压力测试与更少的参数自由度。</p> <p>两个常见误判与失败信号,你可以直接对照检查:</p> <ul> <li>误判:把高胜率当成安全。失败信号:胜率高但盈亏比极差,一次滑点或跳空就吞掉数周利润。</li> <li>误判:认为加仓能“摊平成本”。失败信号:仓位随亏损递增,回撤呈指数型扩大,且停机阈值形同虚设。</li> </ul> <p>还有一个更隐蔽的失败信号是“策略解释权丢失”:当你无法用一句话说明这套EA在什么市场里赚钱、在什么市场里认输,你就不该让它继续自动运行。</p> <h2 id="future-trends-2026">2026趋势:监管、成本与AI对量化的影响</h2> <p>到2026年,EA量化的竞争不再是谁会写指标,而是谁能把数据、执行、风控与合规做成体系。行业报告普遍强调两个方向:其一是更精细的成本与流动性建模,其二是更严格的风险披露与策略透明度要求。对个人与小团队而言,这意味着“更像机构”的流程会成为门槛。</p> <p>AI的影响也更务实:它更适合用来做研究与运维辅助,例如自动归类失败交易、检测参数漂移、生成复盘摘要,而不是替代风控。只要你的仓位管理仍然基于明确阈值,你就能把AI当成放大器,而不是方向盘。</p> <p>如果你希望用更工程化的方式把研究、测试、上线与复盘串起来,建议在建立流程时参考 <a href="https://www.ex-traders.com/">ea量化是什么</a> 的系统化清单:先定义可验证的目标,再把每一步的验收标准写进日志与监控。</p> <h2 id="conclusion">Conclusion</h2> <p>ea量化是什么,说到底是一种把交易从“临场发挥”变成“可执行系统”的方法:策略规则化、执行自动化、结果可评估、风险可约束。它能放大你的优势,也会放大你的漏洞,所以你需要的不是更神的参数,而是更严格的验证与更明确的停机机制。</p> <p>ex-traders 推荐你接下来的行动按可检查标准推进:</p> <ul> <li>用三档成本情景重跑回测:若净收益在压力成本下转负,先别上实盘。</li> <li>设定强制停机阈值:例如最大回撤达到12%或连续亏损10笔即暂停并复盘。</li> <li>做至少4周前向测试:每周核对滑点、点差、成交率与策略预期是否一致。</li> </ul> <h2 id="references">References</h2> <ul> <li>Gartner(2024):关于数据治理与分析能力成熟度的研究,用于支持“流程化与可审计”对结果的重要性。</li> <li>BIS(2023-2024相关研究与简报):对市场微结构、流动性与交易成本变化的讨论,用于支持“成本扰动会显著影响策略净收益”。</li> <li>CFA Institute(2024-2025相关观点与出版物):关于风险管理与模型风险意识的内容,用于支持“停机阈值与样本外验证”的必要性。</li> </ul> <h2 id="faq">FAQ</h2> <h3>ea量化是什么,和普通自动交易有什么差别?</h3> <p>ea量化是什么:用EA把策略写成可执行规则,并用数据验证其稳定性与风险特征。普通“自动交易”可能只是把下单动作自动化,但缺少回测、样本外测试、成本压力测试与停机阈值。差别不在是否自动,而在是否可验证、可复盘、可控风险。</p> <h3>我没有编程基础,也能做EA量化吗?</h3> <p>可以,但要改变预期:你可以先从规则设计、回测评估、参数稳健性与风控阈值入手,再决定自学编程或与开发协作。没有编程基础并不致命,致命的是没有验收标准与复盘习惯。先学会写“交易规则说明书”,再谈写代码。</p> <h3>EA量化需要多少资金才值得开始?</h3> <p>没有固定门槛。更合理的做法是用你能承受的“学习成本”启动:小资金前向测试用于验证执行与成本,等到滑点、成交率、回撤阈值都稳定,再逐步放大仓位。资金越小越要控制频率与成本,避免净收益被费用吞没。</p> <h3>如何判断一个EA是过拟合?</h3> <p>常见迹象包括:参数非常多且微调后曲线变化剧烈;样本外收益显著下降;在不同成本假设下结果从盈利变亏损;盈利高度集中在少数几段历史行情。处理方法是减少自由度、做样本外验证、进行参数扰动测试,并把成本建模纳入回测。</p> <h3>最大回撤应该设多少才合理?</h3> <p>取决于策略类型与交易者承受能力,但必须“先定义再执行”。你可以从权益回撤8%-15%作为常见的风险带,并配合连续亏损停机规则。关键是:回撤阈值一旦触发就必须暂停,进入复盘清单,而不是继续加仓“等它回来”。</p> <h3>同一套EA可以长期不改参数吗?</h3> <p>不建议完全不管。市场结构会变,点差与流动性也会变,参数需要通过定期复核来确认仍然适配。但更不建议频繁调参追逐短期表现。折中做法是设定固定复核周期(例如每月/每季度),用同一套验收指标决定是否调整或停机。</p>

    Import from clipboard

    Paste your markdown or webpage here...

    Advanced permission required

    Your current role can only read. Ask the system administrator to acquire write and comment permission.

    This team is disabled

    Sorry, this team is disabled. You can't edit this note.

    This note is locked

    Sorry, only owner can edit this note.

    Reach the limit

    Sorry, you've reached the max length this note can be.
    Please reduce the content or divide it to more notes, thank you!

    Import from Gist

    Import from Snippet

    or

    Export to Snippet

    Are you sure?

    Do you really want to delete this note?
    All users will lose their connection.

    Create a note from template

    Create a note from template

    Oops...
    This template has been removed or transferred.
    Upgrade
    All
    • All
    • Team
    No template.

    Create a template

    Upgrade

    Delete template

    Do you really want to delete this template?
    Turn this template into a regular note and keep its content, versions, and comments.

    This page need refresh

    You have an incompatible client version.
    Refresh to update.
    New version available!
    See releases notes here
    Refresh to enjoy new features.
    Your user state has changed.
    Refresh to load new user state.

    Sign in

    Forgot password
    or
    Sign in via Google Sign in via Facebook Sign in via X(Twitter) Sign in via GitHub Sign in via Dropbox Sign in with Wallet
    Wallet ( )
    Connect another wallet

    New to HackMD? Sign up

    By signing in, you agree to our terms of service.

    Help

    • English
    • 中文
    • Français
    • Deutsch
    • 日本語
    • Español
    • Català
    • Ελληνικά
    • Português
    • italiano
    • Türkçe
    • Русский
    • Nederlands
    • hrvatski jezik
    • język polski
    • Українська
    • हिन्दी
    • svenska
    • Esperanto
    • dansk

    Documents

    Help & Tutorial

    How to use Book mode

    Slide Example

    API Docs

    Edit in VSCode

    Install browser extension

    Contacts

    Feedback

    Discord

    Send us email

    Resources

    Releases

    Pricing

    Blog

    Policy

    Terms

    Privacy

    Cheatsheet

    Syntax Example Reference
    # Header Header 基本排版
    - Unordered List
    • Unordered List
    1. Ordered List
    1. Ordered List
    - [ ] Todo List
    • Todo List
    > Blockquote
    Blockquote
    **Bold font** Bold font
    *Italics font* Italics font
    ~~Strikethrough~~ Strikethrough
    19^th^ 19th
    H~2~O H2O
    ++Inserted text++ Inserted text
    ==Marked text== Marked text
    [link text](https:// "title") Link
    ![image alt](https:// "title") Image
    `Code` Code 在筆記中貼入程式碼
    ```javascript
    var i = 0;
    ```
    var i = 0;
    :smile: :smile: Emoji list
    {%youtube youtube_id %} Externals
    $L^aT_eX$ LaTeX
    :::info
    This is a alert area.
    :::

    This is a alert area.

    Versions and GitHub Sync
    Get Full History Access

    • Edit version name
    • Delete

    revision author avatar     named on  

    More Less

    Note content is identical to the latest version.
    Compare
      Choose a version
      No search result
      Version not found
    Sign in to link this note to GitHub
    Learn more
    This note is not linked with GitHub
     

    Feedback

    Submission failed, please try again

    Thanks for your support.

    On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?

    Please give us some advice and help us improve HackMD.

     

    Thanks for your feedback

    Remove version name

    Do you want to remove this version name and description?

    Transfer ownership

    Transfer to
      Warning: is a public team. If you transfer note to this team, everyone on the web can find and read this note.

        Link with GitHub

        Please authorize HackMD on GitHub
        • Please sign in to GitHub and install the HackMD app on your GitHub repo.
        • HackMD links with GitHub through a GitHub App. You can choose which repo to install our App.
        Learn more  Sign in to GitHub

        Push the note to GitHub Push to GitHub Pull a file from GitHub

          Authorize again
         

        Choose which file to push to

        Select repo
        Refresh Authorize more repos
        Select branch
        Select file
        Select branch
        Choose version(s) to push
        • Save a new version and push
        • Choose from existing versions
        Include title and tags
        Available push count

        Pull from GitHub

         
        File from GitHub
        File from HackMD

        GitHub Link Settings

        File linked

        Linked by
        File path
        Last synced branch
        Available push count

        Danger Zone

        Unlink
        You will no longer receive notification when GitHub file changes after unlink.

        Syncing

        Push failed

        Push successfully