Full Code of RoyaleAPI/cr-api for AI

Repository: RoyaleAPI/cr-api
Branch: master
Commit: 39de06bfa657
Files: 6
Total size: 9.0 KB

Directory structure:
gitextract_qz_06niq/

├── .github/
│   ├── ISSUE_TEMPLATE.md
│   └── stale.yml
├── .gitignore
├── CNAME
├── CODE_OF_CONDUCT.md
└── README.md

================================================
FILE CONTENTS
================================================

================================================
FILE: .github/ISSUE_TEMPLATE.md
================================================
<!--
USE THIS TEMPLATE. Not using the template will result in invalid issues being closed without a response.
Some guidelines: 
If it’s a question (anything along the lines of “How do I … in Postman”), the answer might lie in our documentation - https://docs.royaleapi.com/
-->

<!-- For Feature requests: -->
### Idea/request:
  1. Briefly explain the idea or request.
  1. Briefly explain the rationale behind the request, or provide a use case.
  1. In which request/endpoint does this apply?
  1. Use the boxes at the bottom of this template to demonstrate a request and expected response.

<!-- For bug reports: -->
### Issue Report:
  1. Did you encounter this recently, or has this bug always been there?
  1. Expected behaviour: 
  1. Console logs (if applicable): 
  1. Screenshots (if applicable):

<!-- Steps to reproduce the problem -->

### Request Details:
<!-- Paste the exact request, including the tag, sent to the server below: -->
```
GET
https://api.royaleapi.com/top/clans
```

### Response Details:
<!-- Paste the exact response received from the server below: -->

```
Code: 200
[...]
```


================================================
FILE: .github/stale.yml
================================================
# Number of days of inactivity before an issue becomes stale
daysUntilStale: 60
# Number of days of inactivity before a stale issue is closed
daysUntilClose: 7
# Issues with these labels will never be considered stale
exemptLabels:
  - pinned
  - security
# Label to use when marking an issue as stale
staleLabel: wontfix
# Comment to post when marking an issue as stale. Set to `false` to disable
markComment: >
  This issue has been automatically marked as stale because it has not had
  recent activity. It will be closed if no further activity occurs. Thank you
  for your contributions.
# Comment to post when closing a stale issue. Set to `false` to disable
closeComment: false


================================================
FILE: .gitignore
================================================
.DS_Store



================================================
FILE: CNAME
================================================
docs.cr-api.com

================================================
FILE: CODE_OF_CONDUCT.md
================================================
# Contributor Covenant Code of Conduct

## Our Pledge

In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.

## Our Standards

Examples of behavior that contributes to creating a positive environment include:

* Using welcoming and inclusive language
* Being respectful of differing viewpoints and experiences
* Gracefully accepting constructive criticism
* Focusing on what is best for the community
* Showing empathy towards other community members

Examples of unacceptable behavior by participants include:

* The use of sexualized language or imagery and unwelcome sexual attention or advances
* Trolling, insulting/derogatory comments, and personal or political attacks
* Public or private harassment
* Publishing others' private information, such as a physical or electronic address, without explicit permission
* Other conduct which could reasonably be considered inappropriate in a professional setting

## Our Responsibilities

Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.

Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.

## Scope

This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.

## Enforcement

Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at our Discord server. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.

Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.

## Attribution

This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version]

[homepage]: http://contributor-covenant.org
[version]: http://contributor-covenant.org/version/1/4/


================================================
FILE: README.md
================================================
<p align="center" style="pointer-events:none"><img src="https://raw.githubusercontent.com/RoyaleAPI/cr-api-docs/master/docs/img/cr-api-logo-b.png" height=
250px" align="right"></p>

# Royale API Support Tracker
<p align="right" style="pointer-events:none">
   <img src="https://img.shields.io/discord/351290254830862337.svg?logo=discord" />
   <img src="https://ga-beacon.appspot.com/UA-105476425-2/RoyaleAPI/readme" />
</p>

If you have a suggestion or an issue to report, please use the [issue tracker](https://github.com/cr-api/cr-api/issues).
We recommend that you search the issue tracker to check if someone else has already reported the issue and whether there is a known solution that you can use. This probably is the fastest way for you to find a solution to any issue that you are facing.

If you are adding a bug report, please add steps to reproduce the bug, exact request (method and URL) and response (including response code). Any additonal information (console errors, screenshots) would be helpful.

### Authors:

<table >
<tr>
<td><a target="_blank" href="https://github.com/smlbiobot"><img src="https://avatars1.githubusercontent.com/u/25040297" height=80px"></a></td>
<td><a target="_blank" href="https://github.com/selfish"><img src="https://avatars0.githubusercontent.com/u/7327741" height=80px"></a></td>
</tr>
<tr>
<td align="center"><a target="_blank" href="https://github.com/smlbiobot">smlbiobot</a></td>
<td align="center"><a target="_blank" href="https://github.com/selfish">Selfish</a></td>
</tr>
</table>

### The Community:

<a target="_blank" href="http://discord.me/RoyaleAPI"><img src="https://discordapp.com/assets/94db9c3c1eba8a38a1fcf4f223294185.png" align="right" height="65px"/></a>If you are interested in talking to the team, we are there on Discord. Feel free to drop by and say hello. Our upcoming features and beta releases are discussed here along with deck advice and Die Hard quotes.

Join our Discord Server from: <a href="http://discord.me/RoyaleAPI">http://discord.me/RoyaleAPI</a>.<br />

<a target="_blank" href="https://www.twitter.com/RoyaleAPI"><img src="https://g.twimg.com/dev/img/marketing/twitter-for-websites/header-logo.png" align="right" height="50px"/></a>We are also available as <a href="https://www.twitter.com/RoyaleAPI">@RoyaleAPI</a> on Twitter. Feel free to drop in a line wherever it is easiest for you. Twitter would be the best place for you to stay updated with latest news, features and releases regarding cr-api.

### Documentation and Tutorials:

If you are looking for more information regarding features and usage of the app, head over to the <a target="_blank" href="https://docs.RoyaleAPI.com">docs site</a>.


### Contribution:

#### Bug Reports & Feature Requests:

Please use the [issue tracker](https://github.com/RoyaleAPI/cr-api/issues) to report any bugs or file feature requests.


### Guidelines for reporting issues:

We have put together a short set of guidelines you can follow while adding an issue to our [GitHub issue tracker](https://github.com/RoyaleAPI/cr-api/issues). Following this should help speedy resolution of issues.

1. Answer to questions along the lines of "How do I... in RoyaleAPI" should be in our online documentation at [https://docs.RoyaleAPI.com](https://docs.RoyaleAPI.com). <!--If you are unable to find a how-to guide in our online documentation, feel free to ask your question on our [Discord Server](#the-community).-->

1. Before reporting an issue use the search feature on the issues page to check if there are issues similar to yours. A lot of issues are duplicates, and it is hard to keep track of them or respond when the issues are solved. If you find your issue already reported, feel free to add "+1" reaction and we will keep a note of it.

1. When reporting a new issue in the issue tracker, check whether it helps to answer the following questions:

   - Is the bug reproducible every time, or do you see it occasionally?
   - Did you first encounter it recently, or has it always been there?
   - If the request/response flow is not working, be sure to check and include details.

### About CR-API:

<a href="https://www.royaleapi.com">www.royaleapi.com</a>