From 3278fd336e2b108ea44c1ac87f6a4d6ab2d2a06c Mon Sep 17 00:00:00 2001
From: YAMAMOTO Takashi <yamamoto@midokura.com>
Date: Thu, 5 Jan 2023 19:52:20 +0900
Subject: [PATCH 1/2] Remove broken CI workflow

---
 .github/workflows/main.yml | 16 ----------------
 1 file changed, 16 deletions(-)
 delete mode 100644 .github/workflows/main.yml

diff --git a/.github/workflows/main.yml b/.github/workflows/main.yml
deleted file mode 100644
index f27c0a2..0000000
--- a/.github/workflows/main.yml
+++ /dev/null
@@ -1,16 +0,0 @@
-name: CI
-on:
-  push:
-    branches: [main]
-  pull_request:
-    branches: [main]
-
-jobs:
-  abi-up-to-date:
-    name: Check ABI files are up-to-date
-    runs-on: ubuntu-latest
-    steps:
-    - uses: actions/checkout@v2
-    - uses: WebAssembly/wit-abi-up-to-date@v2
-      with:
-        wit-abi-tag: wit-abi-0.1.0

From ccd78873c1aff96c27a9879ea1464e5a9b48215b Mon Sep 17 00:00:00 2001
From: YAMAMOTO Takashi <yamamoto@midokura.com>
Date: Thu, 5 Jan 2023 19:53:14 +0900
Subject: [PATCH 2/2] Remove wit-abi stuff we are not using

It's just confusing to have unmaintained files. Let's remove them.
When/if we change our mind, it's trivial to revive them.
---
 proposal-template.abi.md | 31 -------------------------------
 proposal-template.wit.md | 32 --------------------------------
 2 files changed, 63 deletions(-)
 delete mode 100644 proposal-template.abi.md
 delete mode 100644 proposal-template.wit.md

diff --git a/proposal-template.abi.md b/proposal-template.abi.md
deleted file mode 100644
index 9f935ee..0000000
--- a/proposal-template.abi.md
+++ /dev/null
@@ -1,31 +0,0 @@
-# Types
-
-## <a href="#api_type_one" name="api_type_one"></a> `api-type-one`: record
-
-  Short description
-  
-  Explanation for developers using the API.
-
-Size: 16, Alignment: 8
-
-### Record Fields
-
-- <a href="api_type_one.property1" name="api_type_one.property1"></a> [`property1`](#api_type_one.property1): `u64`
-
-
-- <a href="api_type_one.property2" name="api_type_one.property2"></a> [`property2`](#api_type_one.property2): `string`
-
-
-# Functions
-
-----
-
-#### <a href="#api_function_one" name="api_function_one"></a> `api-function-one` 
-
-  Short description
-  
-  Explanation for developers using the API.
-##### Results
-
-- <a href="#api_function_one." name="api_function_one."></a> ``: [`api-type-one`](#api_type_one)
-
diff --git a/proposal-template.wit.md b/proposal-template.wit.md
deleted file mode 100644
index efa5364..0000000
--- a/proposal-template.wit.md
+++ /dev/null
@@ -1,32 +0,0 @@
-# [Proposal Template] API
-
-[This document contains the actual specification. It should be written in the WIT interface definition format. You can find more documentation on the WIT syntax (coming soon!).]
-
-[Note that all comments inside of WIT code blocks will be included in the developer facing documentation for language bindings generated using this WIT file. If there is additional information that needs to be communicated to implementers of the API, then these should be captured in text directly below the code block.]
-
-[If you want to include examples of the API in use, these should be in the README and linked to from this file.]
-
-## api_type_one
-
-```wit
-/// Short description
-///
-/// Explanation for developers using the API.
-record api-type-one {
-    property1: u64,
-    property2: string,
-}
-```
-
-More rigorous specification details for the implementer go here, if needed.
-
-## api_function_one
-
-```wit
-/// Short description
-///
-/// Explanation for developers using the API.
-api-function-one: function() -> api-type-one
-```
-
-If needed, this would explain what a compliant implementation MUST do, such as never returning an earlier result from a later call.