{% load i18n %}
{% if perms.forward_netbox.merge_forwardingestion %}
  {% if object.can_queue_merge %}
    <a href="#"
       hx-get="{% url 'plugins:forward_netbox:forwardingestion_merge' pk=object.pk %}"
       hx-target="#htmx-modal-content"
       class="btn btn-success"
       data-bs-toggle="modal"
       data-bs-target="#htmx-modal">
      <span class="mdi mdi-sync" aria-hidden="true"></span>&nbsp;{% trans "Merge" %}
    </a>
  {% else %}
    <span class="inline-block" tabindex="0" data-bs-toggle="tooltip" data-bs-delay="100" data-bs-placement="bottom">
      <button class="btn btn-success" disabled>
        <i class="mdi mdi-sync" aria-hidden="true"></i>&nbsp;{% trans "Merge" %}
      </button>
    </span>
  {% endif %}
{% endif %}

{% if perms.forward_netbox.merge_forwardingestion and object.can_accept_merge_failures %}
  {# A failed row returns the branch to READY without attesting, so the baseline
     never promotes and every retry hits the same rows. When the failure is
     deterministic that is a dead end, and this is the way out. Separate button,
     separate confirmation: it must never be reachable by clicking Merge twice. #}
  <form method="post"
        action="{% url 'plugins:forward_netbox:forwardingestion_accept_failures' pk=object.pk %}"
        class="d-inline"
        onsubmit="return confirm('Complete this merge and promote the baseline, accepting {{ object.failed_change_count }} failed change(s)? They stay recorded as ingestion issues and the acceptance is attributed to you.');">
    {% csrf_token %}
    <button type="submit" class="btn btn-warning" title="{% trans 'Complete the merge over its recorded failures' %}">
      <span class="mdi mdi-alert-circle-check-outline" aria-hidden="true"></span>&nbsp;{% trans "Accept failures &amp; merge" %}
    </button>
  </form>
{% endif %}