chg: package name

.github/pull_request_templates/ISSUE_TEMPLATE.md

@@ -24,4 +24,4 @@ Steps before creating an issue:
 
 #### Environment
 
-<!-- e.g. Versions used of: npm, Node, chainflow, OS, device -->
+<!-- e.g. Versions used of: npm, Node, chain-indexer-framework, OS, device -->

.github/workflows/release.yml

@@ -7,7 +7,7 @@ on:
 
 jobs:
   Deployment:
-    name: Publish Chainflow
+    name: Publish Chain Indexer Framework
     runs-on: ubuntu-latest
     env: 
       working-directory: ./

CONTRIBUTING.md

@@ -4,21 +4,21 @@ In this guide you will get an overview of the contribution workflow from opening
 
 ## Feature requests
 
-If you find yourself wishing for a feature that doesn't exist in Chainflow, you are probably not alone. There are bound to be others out there with similar needs. Many of the features that Chainflow has today have been added because our users saw the need. Open an issue on our issues list on GitHub which describes the feature you would like to see, why you need it, and how it should work.
+If you find yourself wishing for a feature that doesn't exist in Chain Indexer Framework, you are probably not alone. There are bound to be others out there with similar needs. Many of the features that Chain Indexer Framework has today have been added because our users saw the need. Open an issue on our issues list on GitHub which describes the feature you would like to see, why you need it, and how it should work.
 
 ### How to Get in Touch
 
 Our active Discord community is always ready to help and support new and experienced contributors alike. Link
 
 ## Contributing code and documentation changes
 
-If you would like to contribute a new feature or a bug fix to **Chainflow**, please discuss your idea first on the GitHub issue. If there is no GitHub issue for your idea, please open one. It may be that somebody is already working on it, or that there are particular complexities that you should know about before starting the implementation. There are often a number of ways to fix a problem and it is important to find the right approach before spending time on a PR that cannot be merged.
+If you would like to contribute a new feature or a bug fix to **Chain Indexer Framework**, please discuss your idea first on the GitHub issue. If there is no GitHub issue for your idea, please open one. It may be that somebody is already working on it, or that there are particular complexities that you should know about before starting the implementation. There are often a number of ways to fix a problem and it is important to find the right approach before spending time on a PR that cannot be merged.
 
 We add the `help wanted` label to existing GitHub issues for which community contributions are particularly welcome, and we use the `good first issue` label to mark issues that we think will be suitable for new contributors.
 
 ### Fork and clone the repository
 
-You will need to fork the main **Chainflow** code or documentation repository and clone it to your local machine. See [github help page](https://help.github.com/articles/fork-a-repo) for help.
+You will need to fork the main **Chain Indexer Framework** code or documentation repository and clone it to your local machine. See [github help page](https://help.github.com/articles/fork-a-repo) for help.
 
 Further instructions for specific projects are given below.
 
@@ -41,13 +41,13 @@ Once your changes and tests are ready to submit for review:
 
 2. Rebase your changes
 
-   Update your local repository with the most recent code from the main **Chainflow** repository, and rebase your branch on top of the latest main branch. We prefer your initial changes to be squashed into a single commit. Later, if we ask you to make changes, add them as separate commits. This makes them easier to review. As a final step before merging we will either ask you to squash all commits yourself or we'll do it for you.
+   Update your local repository with the most recent code from the main **Chain Indexer Framework** repository, and rebase your branch on top of the latest main branch. We prefer your initial changes to be squashed into a single commit. Later, if we ask you to make changes, add them as separate commits. This makes them easier to review. As a final step before merging we will either ask you to squash all commits yourself or we'll do it for you.
 
 3. Submit a pull request
 
    Push your local changes to your forked copy of the repository and [submit a pull request](https://help.github.com/articles/using-pull-requests). In the pull request, choose a title which sums up the changes that you have made, and in the body provide more details about what your changes do. Also mention the number of the issue where discussion has taken place, eg "Closes #123".
 
-Then sit back and wait. There will probably be discussion about the pull request and, if any changes are needed, we would love to work with you to get your pull request merged into **Chainflow**.
+Then sit back and wait. There will probably be discussion about the pull request and, if any changes are needed, we would love to work with you to get your pull request merged into **Chain Indexer Framework**.
 
 Please adhere to the general guideline that you should never force push to a publicly shared branch. Once you have opened your pull request, you should consider your branch publicly shared. Instead of force pushing you can just add incremental commits; this is generally easier on your reviewers. If you need to pick up changes from main, you can merge main into your branch. A reviewer might ask you to rebase a long-running pull request in which case force pushing is okay for that request. Note that squashing at the end of the review process should also not be done, that can be done when the pull request is [integrated via GitHub](https://github.com/blog/2141-squash-your-commits).
 
@@ -79,4 +79,4 @@ Read more in [Review Guidelines](./REVIEW.md).
 
 ### License
 
-By contributing to **Chainflow**, you agree that your contributions will be licensed under its [license](./LICENSE).
+By contributing to **Chain Indexer Framework**, you agree that your contributions will be licensed under its [license](./LICENSE).