bevy_input_bindings 0.0.1

High level, flexible and shareable input binding library for the Bevy game engine
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55

# Contributing

First off, thank you for considering contributing to bevy_input_bindings. It's people like you that
will enable bevy_input_bindings to be a useful crate.

## Where do I go from here?

If you've noticed a bug or have a feature request, [make one][new issue]! It's generally best if you
get confirmation of your bug or approval for your feature request this way before starting to code.

## Fork & create a branch

If this is something you think you can fix, then fork kompil and create a branch with a
descriptive name.

A good branch name would be (where issue #145 is the issue you're working on):

```sh
git checkout -b 145-remove-unused-lines
```

## Implement your fix or feature

At this point, you're ready to make your changes! Feel free to ask for help; everyone is a beginner
at first :smile_cat:

## Get the style right

Your patch should follow the same conventions & pass the same code quality checks as the rest of the
project.

You can run `cargo fmt` to format the rust code. This is mandatory for pull requests to be accepted.

## Make a Merge Request

At this point, you should switch back to your master branch and make sure it's up to date with
the master branch:

```sh
git remote add upstream git@gitlab.com:dev.basics/bevy_input_bindings.git
git checkout master
git pull upstream master
```

Then update your feature branch from your local copy of master, and push it!

```sh
git checkout 145-remove-unused-lines
git rebase master
git push --set-upstream origin 145-remove-unused-lines
```

Finally, go to Gitlab and make a Merge Request :D

[new issue]: https://gitlab.com/dev.basics/bevy_input_bindings/-/issues/new