Copy btn

[shareef-dweikat]

---

OP#748

Code Review Checklist

• Description accurately reflects what changes are being made.
• Description explains why the changes are being made (or references an issue containing one).
• The PR appropriately sized.
• New code has enough tests.
• New code has enough documentation to answer "how do I use it?" and "what does it do?".
• Existing documentation is up-to-date, if impacted.

[donpui]

@shareef-dweikat @ewanas should we ignore pushing pubsec.lock?
https://dart.dev/guides/libraries/private-files

[donpui]

@shareef-dweikat @ewanas should we ignore pushing pubsec.lock? https://dart.dev/guides/libraries/private-files

This is solved with another PR