Update LeakyRelu.pbtxt
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this [failed invocation](https://github.com/tensorflow/tensorflow/pull/60522/checks?check_run_id=13282241299) of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request. Please don't use "add file"/"update file"/"fix file"/etc. commit messages. These are hard to reason about when looking at the history of the file/repository. Instead, please write explanatory git commit messages.

The commit message is also the title of the PR if the PR has only one commit. It is thus twice important to have commit messages that are relevant, as PRs would be easier to understand and easier to analyze in search results.

For how to write good quality git commit messages, please consult https://cbea.ms/git-commit/  Hi,
Thanks for helping me improve on my commit message format and also notifying me as to what to do next
Should I continue to work on my pull request or should I close it as it causes an inconvenience for the tensorflow GitHub and also for moderators?

 @cantonios Is my understanding above correct? I'm guessing we'd need to only allow integral types for CPU but not for GPU. Is that possible to do in the same op registration or do we need to have separate op registrations if we want to do this? 

Are there use cases where LeakyRelu is needed to work for integral types? If not, do you think we should just modify the documentation?  > @cantonios Is my understanding above correct? I'm guessing we'd need to only allow integral types for CPU but not for GPU. Is that possible to do in the same op registration or do we need to have separate op registrations if we want to do this?

Your understanding is correct that we need to update the op Attrs to include the type.  If registrations don't exist, you might want to add those as well to actually test it.  You'll need to ensure the kernels will actually work for integers - I haven't looked at the implementation to check.  Otherwise you may need to write new ones.  If it's not that necessary for GPU, it's okay to leave out those kernels/registrations - it would just end up calling the CPU versions (and lead to some host-device data transfers for GPU models).

> Are there use cases where LeakyRelu is needed to work for integral types? If not, do you think we should just modify the documentation?

Maybe for integer-quantized models?  But I generally doubt it.  It's probably easier to update the documentation.
 Hi @swachhandl Any update on this PR? Please. Thank you! Hi @swachhandl Any update on this PR? Please. Thank you! Hi @swachhandl Any update on this PR? Please. Thank you! Sorry I think I didn't get notified for the above pings. I don't have anything to add, awaiting the PR author's reply to my comment above.  This PR is stale because it has been open for 14 days with no activity. It will be closed if no further activity occurs. Thank you. Hi @01-Abdul-Hadi Can you please check @swachhandl's comments and keep us posted ? Thank you! Hi @01-Abdul-Hadi Any update on this PR? Please. Thank you! This PR is stale because it has been open for 14 days with no activity. It will be closed if no further activity occurs. Thank you. This PR was closed because it has been inactive for 14 days since being marked as stale. Please reopen if you'd like to work on this further.
https://github.com/tensorflow/tensorflow/issues/60521 issue no. #60521
"According to doc(https://tensorflow.google.cn/api_docs/python/tf/nn/leaky_relu), the argument features can be float16, float32, float64, int32, int64. But the error message in following snippet code indicates that the type of features can only be float16, float32, float64 without int." This is my first contribution to open source so please excuse any mistake and please tell if anything is wrong.