devtooligan

// SPDX-License-Identifier: UNLICENSED
pragma solidity ^0.8.13;

import "forge-std/Test.sol";

contract SheHateMe {
    receive() external payable {}

    function getImpl(uint8 x) public returns (address) {
        return address(this);

pcaversaccio

// SPDX-License-Identifier: MIT
pragma solidity 0.8.19;

/**
 * @title Returnbomb attack example
 * @author pcaversaccio
 */
contract Evil {
    uint256 public counter;

jefffederman

Naming git branches

tldr; {type}/{group[optional]}/short-form-of-what-it-does

HCM developers consistently use dash-delimited branch names. About half also use f/ and b/ prefixes ('feature' and 'bug', respectively).

I suggest we continue our current practices, specifically:

• a branch should start with a prefix indicating its type: feature/, bug/, chore/, or hotfix/

• prefer the whole word to the one letter abbreviation, the clarity outweighs the cost of the extra characters