Fix issue template

pull/8537/head
Viktor Baranov 1 year ago
parent 89a6b96e83
commit 1d43bb7dc2
  1. 2
      CHANGELOG.md
  2. 22
      ISSUE_TEMPLATE.md

@ -15,7 +15,7 @@
### Chore ### Chore
- [#8536](https://github.com/blockscout/blockscout/pull/8536) - New issue template - [#8536](https://github.com/blockscout/blockscout/pull/8536), [#8537](https://github.com/blockscout/blockscout/pull/8537) - New issue template
- [#8529](https://github.com/blockscout/blockscout/pull/8529) - Move PolygonEdge-related migration to the corresponding ecto repository - [#8529](https://github.com/blockscout/blockscout/pull/8529) - Move PolygonEdge-related migration to the corresponding ecto repository
- [#8504](https://github.com/blockscout/blockscout/pull/8504) - Deploy new UI through Makefile - [#8504](https://github.com/blockscout/blockscout/pull/8504) - Deploy new UI through Makefile
- [#8501](https://github.com/blockscout/blockscout/pull/8501) - Conceal secondary ports in docker compose setup - [#8501](https://github.com/blockscout/blockscout/pull/8501) - Conceal secondary ports in docker compose setup

@ -1,22 +0,0 @@
*Describe your issue here.*
### Environment
* Deployment type (Manual/Docker/Docker-compose):
* Elixir & Erlang/OTP versions (`elixir -version`):
* Node JS version (`node -v`):
* Operating System:
* Blockscout Version/branch/commit:
* Archive node type && version (Erigon/Geth/Nethermind/Ganache/?):
### Steps to reproduce
*Tell us how to reproduce this issue. ❤ if you can push up a branch to your fork with a regression test we can run to reproduce locally.*
### Expected behaviour
*Tell us what should happen.*
### Actual behaviour
*Tell us what happens instead.*
Loading…
Cancel
Save